Changes between Version 1 and Version 2 of Ticket #10534, comment 7


Ignore:
Timestamp:
05/20/18 11:50:47 (3 years ago)
Author:
bonki

Legend:

Unmodified
Added
Removed
Modified
  • Ticket #10534, comment 7

    v1 v2  
    11No worries :-)
    22
    3 Adding breakpoints on lines 138/139 isn't really help unfortunately, the problem is that your breakpoint triggers every time the engine does a {{{seek}}} and it seems that the {{{_handle}}} isn't immediately invalid so the first call is not relevant/interesting.
     3Adding breakpoints on lines 138/139 isn't really helpful unfortunately, the problem is that your breakpoint triggers every time the engine does a {{{seek}}} and it seems that the {{{_handle}}} isn't immediately invalid so the first call is not relevant/interesting.
    44We are only interested in the call to {{{seek}}} when {{{_handle}}} actually is invalid. So you would have to step through all calls and find the one which triggers the assertion if you can't make the debugger you're using provide a backtrace when the assertion already has happened (weird).
    55