public inbox for gdb-patches@sourceware.org
 help / color / mirror / Atom feed
From: "Pierre Muller" <pierre.muller@ics-cnrs.unistra.fr>
To: "'Pedro Alves'" <pedro@codesourcery.com>, <gdb-patches@sourceware.org>
Subject: RE: [RFC] breakpoint.c:  Fix nasty problem with msvcrt DLL on Windows
Date: Fri, 13 Aug 2010 13:50:00 -0000	[thread overview]
Message-ID: <000301cb3aee$7e432c30$7ac98490$@muller@ics-cnrs.unistra.fr> (raw)
In-Reply-To: <201008131215.44484.pedro@codesourcery.com>

> > > -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?

  reply	other threads:[~2010-08-13 13:50 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
2010-08-13 13:50       ` Pierre Muller [this message]
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='000301cb3aee$7e432c30$7ac98490$@muller@ics-cnrs.unistra.fr' \
    --to=pierre.muller@ics-cnrs.unistra.fr \
    --cc=gdb-patches@sourceware.org \
    --cc=pedro@codesourcery.com \
    /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).