Mail Archives: djgpp/1999/05/11/13:20:26
Eli Zaretskii <eliz AT is DOT elta DOT co DOT il> wrote in message
news:Pine DOT SUN DOT 3 DOT 91 DOT 990509121000 DOT 3278T-100000 AT is...
>
> On Sat, 8 May 1999, Andrew Davidson wrote:
>
> > Now I need to keep an eye on temp.p.ph.w with the Rhide
> > debugger and it simply isn't happening. I have added a breakpoint which
is
> > set for file/line. The file and line number are correct and it is
> > highlighting the appropriate line with no problems. However, my
condition
> > for this breakpoint, temp.p.ph.w==0 is being ignored.
>
> Use the `watchpoint' feature. It lets you set a data breakpoint
> instead of code breakpoint.
Right. Erm... how? :)
From within Rhide I would assume this is done by using selecting
'Breakpoints' from within the 'Debug' menu and then setting up the file/line
fields and the condition field.
This is what I am currently doing. However, it doesn't seem to be paying any
attention at all to the value of my variable. It simply acts as a standard
breakpoint and always halts execution at that line. I have set the condition
to be:
if temp->block.p.ph.w==0x2db
Trying variations including bracketing the conditional section (As in C
code), using decimal instead of hexadecimal and using a single '=' sign, but
nothing seems to make any difference. If I watch the variable using 'Watch
an Expression' it seems to be updated acurately so I'd assume I haven't
quite got the conditional notation down yet... all I'm after is stopping the
code on the above condition, nothing fancy.
Incidentally, are there any definitive sources of documentation on GDB or
Rhide's implementation of it? Prefereably something with a simple
step-by-step guide to debugging code that uses graphical video modes and
doing such things as setting watchpoints?
Anyway, thanks for your time,
Andrew
- Raw text -