This is the mail archive of the
gdb-patches@sourceware.org
mailing list for the GDB project.
[PING][RFC] breakpoint.c: Fix nasty problem with msvcrt DLL on Windows
- From: "Pierre Muller" <pierre dot muller at ics-cnrs dot unistra dot fr>
- To: "'Pedro Alves'" <pedro at codesourcery dot com>, <gdb-patches at sourceware dot org>
- Date: Fri, 17 Sep 2010 15:48:08 +0200
- Subject: [PING][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> <201008131215.44484.pedro@codesourcery.com> <000301cb3aee$7e432c30$7ac98490$@muller@ics-cnrs.unistra.fr>
We still didn't take any decision on this patch.
The problem is reported in
http://sourceware.org/bugzilla/show_bug.cgi?id=11886
I cannot debug anything on one of my Windows PC
because it loads and unloads msvcrt.dll at startup;
which leads to the problem.
Pierre Muller
Pascal language support maintainer for GDB
> -----Message d'origine-----
> De?: gdb-patches-owner@sourceware.org [mailto:gdb-patches-
> owner@sourceware.org] De la part de Pierre Muller
> Envoyé?: Friday, August 13, 2010 3:50 PM
> À?: 'Pedro Alves'; gdb-patches@sourceware.org
> Objet?: RE: [RFC] breakpoint.c: Fix nasty problem with msvcrt DLL on
> Windows
>
> > > > -11 longjmp master keep n 0x77c06d74 inf 1
> > > >
> > > > (gdb) n
> > > > Warning:
> > > > Cannot insert breakpoint -11.
> > > > Error accessing memory address 0x77c06d74: Input/Output error.
>
> > 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?
>
>
> I was unable to reproduce that issue,
> and I suspect that this is just an error on me side:
> I probably just copied parts of two different gdb sessions.
>
> When trying to reproduce it, I always got internal (negative) numbers
> that were different (more negative, meaning created later)
> for the "longjmp" breakpoints as compared to their "longjmp master"
> equivalent.
>
> Sorry to have generated that confusion,
>
> Pierre
>
> PS: could you test and confirm the bug report 11886?