Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Daniel Jacobowitz <drow@false.org>
To: Michael Veksler <mveksler@tx.technion.ac.il>
Cc: Thomas Neumann <tneumann@users.sourceforge.net>, gdb@sourceware.org
Subject: Re: Organization of breakpoint locations
Date: Mon, 19 Feb 2007 21:24:00 -0000	[thread overview]
Message-ID: <20070219144758.GA32582@caradoc.them.org> (raw)
In-Reply-To: <45D9B6EA.6050309@tx.technion.ac.il>

On Mon, Feb 19, 2007 at 04:40:42PM +0200, Michael Veksler wrote:
> I always thought (speculated) that breakpoint removal was to simplify 
> things like
> 
>    (gdb) x /i $pc
> 
> Where you don't want to see the INT instruction, but the original value.

Some parts of GDB won't work if we leave breakpoints in.  But, it's
not hard to fix - we have the right helper routines for it nowadays.
Joel made some changes like this in the last year.

> GDB crash does sound like another reason.
> Being curios, I'd like to ask what was the original reason for
> this behavior? Does anyone know? I never saw it documented anywhere.

I don't know either; I'm just guessing.  It may have just been easiest
at the time and no one came back to think about it later.

-- 
Daniel Jacobowitz
CodeSourcery


  reply	other threads:[~2007-02-19 14:48 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-02-19 11:57 Thomas Neumann
2007-02-19 12:54 ` Daniel Jacobowitz
2007-02-19 14:40   ` Thomas Neumann
2007-02-19 14:48     ` Daniel Jacobowitz
2007-02-19 14:54       ` Michael Veksler
2007-02-19 21:24         ` Daniel Jacobowitz [this message]
2007-02-20  4:46       ` Thomas Neumann
2007-02-20 10:26         ` Thomas Neumann
2007-02-21 17:05   ` Michael Snyder
2007-02-21  1:53 ` Michael Snyder

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=20070219144758.GA32582@caradoc.them.org \
    --to=drow@false.org \
    --cc=gdb@sourceware.org \
    --cc=mveksler@tx.technion.ac.il \
    --cc=tneumann@users.sourceforge.net \
    /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