From: Eli Zaretskii <eliz@gnu.org>
To: Nick Roberts <nickrob@snap.net.nz>
Cc: drow@false.org, vladimir@codesourcery.com,
gdb-patches@sources.redhat.com
Subject: Re: delete_breakpoint: don't try to insert other breakpoints
Date: Sat, 17 Nov 2007 09:13:00 -0000 [thread overview]
Message-ID: <uk5ohck07.fsf@gnu.org> (raw)
In-Reply-To: <18238.3787.459206.333769@kahikatea.snap.net.nz> (message from Nick Roberts on Sat, 17 Nov 2007 10:42:35 +1300)
> From: Nick Roberts <nickrob@snap.net.nz>
> Date: Sat, 17 Nov 2007 10:42:35 +1300
> Cc: Daniel Jacobowitz <drow@false.org>, 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).
>
> I've run the testsuite using my asynchronous version of GDB, with and
> without Vladimir's change and, in fact, there was one less failure and
> seven more passes with it. Notably, the extra passes with print-threads.exp
> involved breakpoints.
That's because we don't allow deleting breakpoints asynchronously even
in the async version, AFAIK.
next prev parent reply other threads:[~2007-11-17 9:13 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
2007-11-16 21:44 ` Nick Roberts
2007-11-16 22:24 ` Vladimir Prus
2007-11-17 9:13 ` Eli Zaretskii [this message]
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=uk5ohck07.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=drow@false.org \
--cc=gdb-patches@sources.redhat.com \
--cc=nickrob@snap.net.nz \
--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