|
OTOH, you are correct that I started debug after the program crashed. In my experience, that has never made a difference in being able to view the values of fields used by the program with the debugger EVAL command vs F11.
I don't know why F11 works and EVAL doesn't. And I don't really understand what's going on under the covers.
It's just been my experience that when a program crashes, it becomes difficult to view (or change) the contents of variables. It sounds like you've had the exact opposite experience :) I haven't explored it further than that, my solution has been to set a breakpoint on the line that I know it'll crash on, and then run the program again and reproduce the problem. This way, it'll hit the breakpoint before it crashes, and I can see everything that's going on.
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.
midrange.com
