Path: utzoo!utgpu!cunews!bnrgate!brtph3!brchh104!brchs1!bnr.ca!rice.edu!sun-spots-request From: erf@progress.COM (Eric Feigenson) Newsgroups: comp.sys.sun Subject: Problem With dbx(tool) with SunOS 4.1 Keywords: Miscellaneous Message-ID: <1971@brchh104.bnr.ca> Date: 18 Mar 91 17:28:00 GMT Sender: news@brchh104.bnr.ca Organization: Sun-Spots Lines: 25 Approved: Sun-Spots@rice.edu X-Original-Date: Wed, 6 Mar 91 13:09:18 EST X-Sun-Spots-Digest: Volume 10, Issue 57, message 7 X-Note: Submissions: sun-spots@rice.edu, Admin: sun-spots-request@rice.edu I'm on a Sun 3/60 running SunOS 4.1. I'm using dbxtool to do some debugging. According to the documentation, I should be able to do: stop if where the stop happens if is TRUE. This has never worked for me. I admit I haven't tried it very often since I've never gotten it to work. My current specific instance is: (3) stop if *(char *) 1051572 != 97 When I enter this stop command, the is false. Once I resume execution however, dbx never stops execution when the value changes; it stops only when it hits another (unconditional) breakpoint. It doesn't even seem to be running any slower, which it should if it's checking the condition on every statement. Am I doing something obviously wrong here? Any and all help would be appreciated! Thanks in advance! Eric R. Feigenson UUCP: mit-eddie!progress!erf Progress Software Corp. Internet: erf@progress.com 5 Oak Park Bedford, MA 01730