delorie.com/archives/browse.cgi | search |
Sender: | root AT delorie DOT com |
Message-ID: | <37387481.F06C6FD4@inti.gov.ar> |
Date: | Tue, 11 May 1999 15:18:41 -0300 |
From: | salvador <salvador AT inti DOT gov DOT ar> |
Organization: | INTI |
X-Mailer: | Mozilla 4.51 [en] (X11; I; Linux 2.0.36 i686) |
X-Accept-Language: | es-AR, en, es |
MIME-Version: | 1.0 |
To: | djgpp AT delorie DOT com |
Subject: | Re: Setting breakpoints on variable values in Rhide? |
References: | <Pine DOT SUN DOT 3 DOT 91 DOT 990509121000 DOT 3278T-100000 AT is> <7h9njo$3kk$1 AT news6 DOT svr DOT pol DOT co DOT uk> |
Reply-To: | djgpp AT delorie DOT com |
Andrew Davidson wrote: > >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 > That's an invalid condition, just use temp->block.p.ph.w==0x2db SET
webmaster | delorie software privacy |
Copyright © 2019 by DJ Delorie | Updated Jul 2019 |