From: Eli Zaretskii <eliz@gnu.org>
To: Daniel Jacobowitz <drow@false.org>
Cc: vladimir@codesourcery.com, gdb-patches@sources.redhat.com
Subject: Re: delete_breakpoint: don't try to insert other breakpoints
Date: Fri, 16 Nov 2007 15:09:00 -0000 [thread overview]
Message-ID: <ulk8ycjmy.fsf@gnu.org> (raw)
In-Reply-To: <20071116130250.GA31441@caradoc.them.org> (message from Daniel Jacobowitz on Fri, 16 Nov 2007 08:02:50 -0500)
> Date: Fri, 16 Nov 2007 08:02:50 -0500
> From: Daniel Jacobowitz <drow@false.org>
> Cc: Vladimir Prus <vladimir@codesourcery.com>,
> gdb-patches@sources.redhat.com
>
> Eli, how is code which will never be reached a feature?
The code is never reached only as long as breakpoints are deleted
synchronously (because we remove the breakpoint instruction as soon as
the inferior stops).
next prev parent reply other threads:[~2007-11-16 15:09 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-11-14 20:24 Vladimir Prus
2007-11-15 4:04 ` Eli Zaretskii
2007-11-15 5:59 ` Vladimir Prus
2007-11-16 10:13 ` Eli Zaretskii
2007-11-16 10:34 ` Vladimir Prus
2007-11-16 11:15 ` Eli Zaretskii
2007-11-16 13:02 ` Daniel Jacobowitz
2007-11-16 14:14 ` Vladimir Prus
2007-11-16 15:09 ` Eli Zaretskii [this message]
2007-11-16 21:44 ` Nick Roberts
2007-11-16 22:24 ` Vladimir Prus
2007-11-17 9:13 ` Eli Zaretskii
2007-11-18 1:25 ` Nick Roberts
2007-12-16 21:13 ` Daniel Jacobowitz
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=ulk8ycjmy.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=drow@false.org \
--cc=gdb-patches@sources.redhat.com \
--cc=vladimir@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