I use the UniDebugger almost exclusively for all my programming. The only time I've had a problem with it not finishing is if I get into a program that is either looping or waiting for some kind of input. You can usually see which program you're in by looking at the Call Stack pane (Alt-4). This is probably only going to help if you're stepping through the programs, though. If you hit F5 for GO, though, you're going to lose the detail line by line execution display.
Reset does cause an interrupt to be sent so that is a brute-force method of getting out of trouble. Another thing to keep in mind is the number of variables you're watching. The more there are the longer it takes to execute the step from line to line. HTH's, BobW -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of [EMAIL PROTECTED] Sent: Wednesday, April 05, 2006 11:18 AM To: u2-users@listserver.u2ug.org Cc: [EMAIL PROTECTED] Subject: RE: [U2] Newest UV UniDebugger I don't have a problem with it going past a breakpoint. I have had trouble with it not realizing the "debugging" is done. The "reset" option under the debug menu appears to be there to "fix" the issue - but it doesn't seem to work. Hth Colin Alfke Calgary Canada ------- u2-users mailing list u2-users@listserver.u2ug.org To unsubscribe please visit http://listserver.u2ug.org/
