d000hg My post count is Majestic Joined Dec 1, 2007 Messages 38,987 Likes received 2,910 Thanks received 678 Location My house Jan 22, 2016 19:30 #1 When the cause of the crash in your application turns out to be the debugging/tracing code you added to see what was going on.
When the cause of the crash in your application turns out to be the debugging/tracing code you added to see what was going on.
NickFitz I post more often than I breathe Joined Jun 18, 2007 Messages 65,838 Likes received 32,657 Thanks received 10,042 Location Your local branch Jan 23, 2016 09:09 #2 d000hg said: When the cause of the crash in your application turns out to be the debugging/tracing code you added to see what was going on. Click to expand... Or, indeed, the other way round: you add the debug/trace code, it stops crashing. Remove it, it crashes again
d000hg said: When the cause of the crash in your application turns out to be the debugging/tracing code you added to see what was going on. Click to expand... Or, indeed, the other way round: you add the debug/trace code, it stops crashing. Remove it, it crashes again
NotAllThere Permie Swiss Moderator Joined Aug 27, 2007 Messages 28,185 Likes received 8,675 Thanks received 2,403 Location Far away from HMRC Jan 23, 2016 10:34 #3 What runs perfectly (and debuggerable) in foreground will fail in background.
RSoles Contractor Among Contractors Joined Jul 6, 2005 Messages 1,208 Likes received 168 Thanks received 43 Location The Isle of Alassi Jan 23, 2016 11:28 #4 Ah yes, I remember a card which worked perfectly on an extender, back in the rack, dead as a dead thing.
Ah yes, I remember a card which worked perfectly on an extender, back in the rack, dead as a dead thing.