Problem With dbx(tool) with SunOS 4.1
Eric Feigenson
erf at progress.COM
Tue Mar 19 03:28:00 AEST 1991
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 <condition>
where the stop happens if <condition> 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 <condition> 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 at progress.com
5 Oak Park
Bedford, MA 01730
More information about the Comp.sys.sun
mailing list