madd@adt.UUCP (jim frost) (04/25/89)
It would interest me a great deal to find out why dbx sometimes confuses a breakpoint with termination of the program. For instance: (dbx) stop in trWriteScreen [3] stop in trWriteScreen (dbx) run Process 23700 (padsu_v2.2b) started [...] Process 23700 (padsu_v2.2b) finished (dbx) quit It did not finish, it hit the breakpoint I had set. A debugger which confuses termination and breakpoints is less than useful. jim frost madd@bu-it.bu.edu
madd@adt.UUCP (jim frost) (04/25/89)
>> It would interest me a great deal to find out why dbx sometimes >> confuses a breakpoint with termination of the program. For instance: >>[...] >If the program is a graphics program, you need to call foreground () before >any other executable statement. Graphics programs run in the background by >default, so when you execute the code within dbx, the message "terminated >normally" appears as soon as you press return. The program is running in the foreground and the breakpoints *sometimes* are interpreted as termination by the debugger. It's inconsistent and difficult to reproduce, but it happens. jim