You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I had some code that was accidentally doing a divide by zero. It basically looked like this:
volatileunsignedzero=0; // `volatile` so the compiler doesn't notice the divide by 0unsignedbad_value= (zero % zero); // <-- debugger stalls with no feedback here
It took me a few extra moments to track down because I wasn't getting any feedback from the debugger. It showed my app in a green running state, even though execution stopped on the line that threw the exception. Should the debugger go into its red-coloured error state in this case? Is it possible to output an error message about the exception?
(This may be the same request as #120--not sure!).
The text was updated successfully, but these errors were encountered:
I had some code that was accidentally doing a divide by zero. It basically looked like this:
It took me a few extra moments to track down because I wasn't getting any feedback from the debugger. It showed my app in a green running state, even though execution stopped on the line that threw the exception. Should the debugger go into its red-coloured error state in this case? Is it possible to output an error message about the exception?
(This may be the same request as #120--not sure!).
The text was updated successfully, but these errors were encountered: