RE: [RFC] breakpoint.c: Fix nasty problem with msvcrt DLL on Windows

["Pierre Muller" <pierre.muller@ics-cnrs.unistra.fr>]

 If I understood the code correctly,
"longjmp master" breakpoints type are internal breakpoints
that stay always disabled and never get enabled.

  Their function is to list all possible functions
that might do long jumps (i.e. modify the stack directly)
and trigger the creation of a normal "longjmp" breakpoint,
via a call to "set_longjmp_breakpoint" function.
This function is called only once in step_1 function in infcmd.c 
source.

The normal "longjmp" breakpoints are deleted at each stop,
by a call to "delete_longjmp_breakpoint" (2 such calls
exist, one is part of a cleanup in case an error
appears).

  Thus, when calling "maint info breakpoints" command,
only "longjmp master" internal breakpoint types are listed.

  If my analysis is correct, the answer to your two questions
is no.
 
Pierre

> -----Message d'origine-----
> De : gdb-patches-owner@sourceware.org [mailto:gdb-patches-
> owner@sourceware.org] De la part de Pedro Alves
> Envoyé : Thursday, August 12, 2010 5:43 PM
> À : gdb-patches@sourceware.org
> Cc : Pierre Muller
> Objet : Re: [RFC] breakpoint.c: Fix nasty problem with msvcrt DLL on
> Windows
> 
> 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.
> 
> --
> Pedro Alves