From: Pedro Alves <pedro@codesourcery.com>
To: gdb-patches@sourceware.org
Cc: "Pierre Muller" <pierre.muller@ics-cnrs.unistra.fr>
Subject: Re: [RFC] breakpoint.c: Fix nasty problem with msvcrt DLL on Windows
Date: Fri, 13 Aug 2010 11:15:00 -0000 [thread overview]
Message-ID: <201008131215.44484.pedro@codesourcery.com> (raw)
In-Reply-To: <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
next prev parent reply other threads:[~2010-08-13 11:15 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-08-05 11:35 Pierre Muller
2010-08-05 12:12 ` Pierre Muller
2010-08-12 15:42 ` Pedro Alves
2010-08-13 8:47 ` Pierre Muller
2010-08-13 11:15 ` Pedro Alves [this message]
2010-08-13 13:50 ` Pierre Muller
2010-09-17 19:56 ` [PING][RFC] " Pierre Muller
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=201008131215.44484.pedro@codesourcery.com \
--to=pedro@codesourcery.com \
--cc=gdb-patches@sourceware.org \
--cc=pierre.muller@ics-cnrs.unistra.fr \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).