Changes between Version 1 and Version 2 of Ticket #15728, comment 26


Ignore:
Timestamp:
Aug 16, 2020, 5:56:45 PM (4 years ago)
Author:
ttcoder

Legend:

Unmodified
Added
Removed
Modified

  • Ticket #15728, comment 26

    v1 v2  
    1818- "w:908:offscreen ("Reason : _numblock >0")
    1919- "w:xxx:offscreen ("Reason : Segment Violation")
     20
     21EDIT: yup it got captured in the syslog (retrieved over from my beta1 partition) each time, e.g.:
     22
     23{{{
     24KERN: 1000: DEBUGGER: _numBlocks > 0
     25KERN: debug_server: Thread 1000 entered the debugger: Debugger call: `_numBlocks > 0'
     26KERN: stack trace, current PC 0x1d7240d01c1  _kern_debugger + 0x9:
     27KERN:   (0x7f30c3894cc0)  0x1d72415bd02  free + 0x42
     28KERN:   (0x7f30c3894ce0)  0x118e7531921  _ZN7PainterD0Ev + 0x11 (..)
     29KERN:   (0x7f30c3894d00)  0x118e7522480  _ZN13DrawingEngineD2Ev + 0x30 (..)
     30KERN:   (0x7f30c3894f10)  0x118e751b81b  _ZN9AlphaMask9_GenerateEv + 0x4b (..)
     31}}}
     32
     33
    2034So if I'm not completely mis-understanding this, it's possible that the sequence of events is 1) Web+ crashes, 2) debbugger attempts to open its normal BAlert, 3) that crashes the app_server 4) debugger is invoked a second time, but this time in "console" mode. Though I suppose that sequence does not make a huge difference compared to the previously assumed one.
    2135