public inbox for gdb-prs@sourceware.org
help / color / mirror / Atom feed
From: "xdje42 at gmail dot com" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug cli/17222] printf_filtered vs printf_unfiltered
Date: Sun, 31 Aug 2014 22:11:00 -0000 [thread overview]
Message-ID: <bug-17222-4717-YXrKWmQst1@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-17222-4717@http.sourceware.org/bugzilla/>
https://sourceware.org/bugzilla/show_bug.cgi?id=17222
Doug Evans <xdje42 at gmail dot com> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |xdje42 at gmail dot com
--- Comment #1 from Doug Evans <xdje42 at gmail dot com> ---
infcmd.c:signal_command is another example of an odd mix of printf_filtered and
printf_unfiltered:
if (!non_stop)
{
struct thread_info *tp;
ptid_t resume_ptid;
int must_confirm = 0;
/* This indicates what will be resumed. Either a single thread,
a whole process, or all threads of all processes. */
resume_ptid = user_visible_resume_ptid (0);
ALL_NON_EXITED_THREADS (tp)
{
if (ptid_equal (tp->ptid, inferior_ptid))
continue;
if (!ptid_match (tp->ptid, resume_ptid))
continue;
if (tp->suspend.stop_signal != GDB_SIGNAL_0
&& signal_pass_state (tp->suspend.stop_signal))
{
if (!must_confirm)
printf_unfiltered (_("Note:\n"));
printf_unfiltered (_(" Thread %d previously stopped with signal
%s, %s.\n"),
tp->num,
gdb_signal_to_name (tp->suspend.stop_signal),
gdb_signal_to_string
(tp->suspend.stop_signal));
must_confirm = 1;
}
}
if (must_confirm
&& !query (_("Continuing thread %d (the current thread) with
specified signal will\n"
"still deliver the signals noted above to their
respective threads.\n"
"Continue anyway? "),
inferior_thread ()->num))
error (_("Not confirmed."));
}
if (from_tty)
{
if (oursig == GDB_SIGNAL_0)
printf_filtered (_("Continuing with no signal.\n"));
else
printf_filtered (_("Continuing with signal %s.\n"),
gdb_signal_to_name (oursig));
}
--
You are receiving this mail because:
You are on the CC list for the bug.
next prev parent reply other threads:[~2014-08-31 22:11 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-01 16:58 [Bug cli/17222] New: " dje at google dot com
2014-08-31 22:11 ` xdje42 at gmail dot com [this message]
2021-12-27 6:31 ` [Bug cli/17222] " tromey at sourceware dot org
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-17222-4717-YXrKWmQst1@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).