Mail Archives: djgpp/2000/06/20/17:32:50
Hello.
Eli Zaretskii wrote:
> 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.
I didn't say that I understood why this was happening. I only observed
that gdb would not break when I used normal breakpoints; I could make it
break using hardware breakpoints. I have no idea if Windows is removing
the instructions. I have not tried to investigate this problem further,
since I was debugging libsocket at the time.
As a side issue, gdb crashes VMware (running Windows '95 or NT). If you
set a breakpoint, then gdb breaks and then you single-step (using s or n),
then VMware will crash. I reported this to the VMware folks and sent them
some code so they could reproduce this problem. They have not got back to
me. They said at the time that VMware was not really debugger-friendly
(i.e. debugging doesn't generally work under it), so I don't think this is
limited to gdb.
Bye,
--
Richard Dawe
[ mailto:richdawe AT bigfoot DOT com | http://www.bigfoot.com/~richdawe/ ]
- Raw text -