Message-Id: <200006202008.XAA23539@mailgw1.netvision.net.il> Date: Tue, 20 Jun 2000 23:09:27 +0200 X-Mailer: Emacs 20.6 (via feedmail 8.1.emacs20_6 I) and Blat ver 1.8.5b From: "Eli Zaretskii" To: Richard Dawe CC: djgpp AT delorie DOT com In-reply-to: <394F7467.6340126B@phekda.freeserve.co.uk> (message from Richard Dawe on Tue, 20 Jun 2000 14:40:55 +0100) Subject: Re: preprpcessor for overiding gcc optimation switch References: <83zop3o170 DOT fsf AT mercury DOT bitbucket> <25c58271 DOT fc969396 AT usw-ex0104-033 DOT remarq DOT com> <8ino7d$i9b$1 AT nets3 DOT rz DOT RWTH-Aachen DOT DE> <394F7467 DOT 6340126B AT phekda DOT freeserve DOT co DOT uk> Reply-To: djgpp AT delorie DOT com Errors-To: nobody AT delorie DOT com X-Mailing-List: djgpp AT delorie DOT com X-Unsubscribes-To: listserv AT delorie DOT com Precedence: bulk > From: Richard Dawe > Newsgroups: comp.os.msdos.djgpp > Date: Tue, 20 Jun 2000 14:40:55 +0100 > > When I have done debugging on libsocket, I found that normal breakpoints > failed to work sometimes. I found that hardware breakpoints were much more > successful - e.g. "hb lsck_init". Otherwise gdb would not stop in the > routine that I asked it to. I guessed that this was some problem due to > libsocket calling in Windows virtual device drivers. I fail to see how calling a VxD can disable a breakpoint. A breakpoint is a special instruction written to the program's code; unless Windows is smart enough to remove that special instruction and replace it with the original one, it can do nothing to interfere.