This is the mail archive of the
gdb-patches@sourceware.org
mailing list for the GDB project.
Re: [RFC] breakpoint.c: Fix nasty problem with msvcrt DLL on Windows
- From: Pedro Alves <pedro at codesourcery dot com>
- To: gdb-patches at sourceware dot org
- Cc: "Pierre Muller" <pierre dot muller at ics-cnrs dot unistra dot fr>
- Date: Fri, 13 Aug 2010 12:15:44 +0100
- Subject: Re: [RFC] breakpoint.c: Fix nasty problem with msvcrt DLL on Windows
- References: <002a01cb3492$5ba5c050$12f140f0$@muller@ics-cnrs.unistra.fr> <201008121642.47284.pedro@codesourcery.com> <000301cb3ac4$107d4fc0$3177ef40$@muller@ics-cnrs.unistra.fr>
(Please don't top post.)
On Friday 13 August 2010 09:46:46, Pierre Muller wrote:
> > On Thursday 05 August 2010 12:35:51, Pierre Muller wrote:
> > > (gdb) maint inf b
> > > Num Type Disp Enb Address What
> > > -10 longjmp master keep n 0x61093868 <longjmp> inf 1
> > > -11 longjmp master keep n 0x77c06d74 inf 1
> > >
> > > (gdb) n
> > > Warning:
> > > Cannot insert breakpoint -11.
> > > Error accessing memory address 0x77c06d74: Input/Output error.
> >
> > 1. Did we really try to insert a Enb=n breakpoint?
> > 2. Did we really try to insert a longjmp master breakpoint?
> >
> > If yes to any of those, something else is broken.
> If I understood the code correctly,
> "longjmp master" breakpoints type are internal breakpoints
> that stay always disabled and never get enabled.
(...)
> If my analysis is correct, the answer to your two questions
> is no.
Your analysis is correct. But then why did gdb print
"Cannot insert breakpoint -11.", with -11 being the
number of one of the internal longjmp master breakpoints?
Are we copying the breakpoint number when creating the
longjmp momentary breakpoints from the master, meaning that's
a red herring (though one that I'd like fixed), or is there
something else really broken?
--
Pedro Alves