agraham Expert Licensed User Longtime User Jul 20, 2011 #1 If the debugger is attached and an uncaught exception occurs then I get the "paused" message on the device showing the line which errored and don't get the exception details dialog until I step or run the program. Code: Dim ba As Byte If ba = Null Then 'exception causes pause here with no breakpoint set ... End If Is this by design, a bug or an unavoidable consequence of the debugger architecture?
If the debugger is attached and an uncaught exception occurs then I get the "paused" message on the device showing the line which errored and don't get the exception details dialog until I step or run the program. Code: Dim ba As Byte If ba = Null Then 'exception causes pause here with no breakpoint set ... End If Is this by design, a bug or an unavoidable consequence of the debugger architecture?
nfordbscndrd Well-Known Member Licensed User Longtime User Jul 20, 2011 #2 That's the way it worked in 1.5. I just always assumed it was intended to work that way, buy maybe it wasn't...
That's the way it worked in 1.5. I just always assumed it was intended to work that way, buy maybe it wasn't...
Erel B4X founder Staff member Licensed User Longtime User Jul 21, 2011 #3 This is by design. You can see the exception in the variables section under LastException. It should appear red. Note that if the exception happens in a service then the next step after this pause is that your program crashes and exits.
This is by design. You can see the exception in the variables section under LastException. It should appear red. Note that if the exception happens in a service then the next step after this pause is that your program crashes and exits.
