dbx problems on 4D

[jim frost]

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 at bu-it.bu.edu