From: Daniel Jacobowitz <drow@false.org>
To: Fabian Cenedese <Cenedese@indel.ch>
Cc: gdb@sources.redhat.com
Subject: Re: Auto removing BPs on stop
Date: Fri, 10 Sep 2004 15:18:00 -0000 [thread overview]
Message-ID: <20040910151834.GB2103@nevyn.them.org> (raw)
In-Reply-To: <5.2.0.9.1.20040910135924.01d27220@NT_SERVER>
On Fri, Sep 10, 2004 at 02:08:16PM +0200, Fabian Cenedese wrote:
> Hi
>
> Whenever the target stops gdb will remove all breakpoints from the target
> and set them again before stepping/continuing. What functionality in gdb
> depends on this? Backtrace? Breakpoint handling?
> In our multitasking system a thread can stop on a breakpoint while the
> others are still running, so the breakpoints are still useful and shouldn't
> be removed.
GDB can't cope with this. GDB assumes that when it is told that the
inferior has "stopped", its state will not change, and all threads can
be examined.
> What would break in gdb if I just removed those calls to unset/re-set
> the breakpoints? I know that the setting is partly necessary as new
> breakpoints aren't yet set.
I don't know. A lot of places may still read target memory without
using the routines that "remove" breakpoints from GDB's image of target
memory, for one thing; this is slowly being fixed.
My goal is to stop the needless removing and reinserting some day, but
I don't think it will work yet.
--
Daniel Jacobowitz
next prev parent reply other threads:[~2004-09-10 15:18 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-09-10 12:09 Fabian Cenedese
2004-09-10 15:18 ` Daniel Jacobowitz [this message]
2004-09-13 9:32 ` Fabian Cenedese
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=20040910151834.GB2103@nevyn.them.org \
--to=drow@false.org \
--cc=Cenedese@indel.ch \
--cc=gdb@sources.redhat.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