Path: utzoo!attcan!uunet!cs.utexas.edu!tut.cis.ohio-state.edu!ucbvax!adt.UUCP!madd
From: madd@adt.UUCP (jim frost)
Newsgroups: comp.sys.sgi
Subject: dbx problems on 4D
Message-ID: <8904241855.AA29198@adt.uucp>
Date: 24 Apr 89 18:55:03 GMT
Sender: daemon@ucbvax.BERKELEY.EDU
Organization: The Internet
Lines: 16

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