public inbox for gdb-prs@sourceware.org
help / color / mirror / Atom feed
From: "palves at redhat dot com" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug gdb/16809] interrupt -a
Date: Tue, 15 Jul 2014 21:21:00 -0000 [thread overview]
Message-ID: <bug-16809-4717-SYx4BaG2un@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-16809-4717@http.sourceware.org/bugzilla/>
https://sourceware.org/bugzilla/show_bug.cgi?id=16809
--- Comment #13 from Pedro Alves <palves at redhat dot com> ---
> Does pagination still break non-stop? If not, remove the relevant text from
> gdb/doc/gdb.texinfo , node "Non-Stop mode", line 5781-5784.
Yeah, that text could use an update / clarification, thanks.
It doesn't break it in the sense that there are no other known issues that
weren't fixed by the fixes for PR17072 (both in master and 7.8).
But it still "breaks" it in the sense that if pagination occurs, target event
processing is paused until the user proceeds with the pagination. So, e.g., if
the target needs hits a breakpoint that isn't supposed to be reported and needs
to be stepped over, it'll remain paused until the pagination is proceeded.
--
You are receiving this mail because:
You are on the CC list for the bug.
prev parent reply other threads:[~2014-07-15 21:21 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-04 20:00 [Bug gdb/16809] New: " dilyan.palauzov at aegee dot org
2014-07-12 19:02 ` [Bug gdb/16809] " xdje42 at gmail dot com
2014-07-13 21:58 ` dilyan.palauzov at aegee dot org
2014-07-13 23:30 ` dilyan.palauzov at aegee dot org
2014-07-14 0:19 ` xdje42 at gmail dot com
2014-07-14 0:30 ` xdje42 at gmail dot com
2014-07-14 0:51 ` xdje42 at gmail dot com
2014-07-14 3:10 ` xdje42 at gmail dot com
2014-07-15 6:18 ` dje at google dot com
2014-07-15 8:19 ` palves at redhat dot com
2014-07-15 19:48 ` dilyan.palauzov at aegee dot org
2014-07-15 19:58 ` xdje42 at gmail dot com
2014-07-15 19:59 ` xdje42 at gmail dot com
2014-07-15 21:21 ` palves at redhat dot com [this message]
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=bug-16809-4717-SYx4BaG2un@http.sourceware.org/bugzilla/ \
--to=sourceware-bugzilla@sourceware.org \
--cc=gdb-prs@sourceware.org \
/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).