Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Joel Brobecker <brobecker@adacore.com>
To: Pedro Alves <pedro@codesourcery.com>, gdb-patches@sourceware.org
Subject: Re: Don't paginate "new thread" events
Date: Wed, 12 Mar 2008 16:03:00 -0000	[thread overview]
Message-ID: <20080312160306.GB3738@adacore.com> (raw)
In-Reply-To: <20080312031329.GA12967@caradoc.them.org>

> The one most frequently encountered, in linux-thread-db.c,
> was already unfiltered for this very reason.

Ooops, right! A grep instead of a visual read of Vladimir's patch
shows very clearly that there were already 3 locations where we used
to use the printf unfiltered. So Pedro's patch is definitely OK.

2008-03-12  Pedro Alves  <pedro@codesourcery.com>

	* thread.c (add_thread): Use printf_unfiltered to print.

This should go to the branch as well.


---
 gdb/thread.c |    2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

Index: src/gdb/thread.c
===================================================================
--- src.orig/gdb/thread.c	2008-03-12 01:36:24.000000000 +0000
+++ src/gdb/thread.c	2008-03-12 01:36:42.000000000 +0000
@@ -136,7 +136,7 @@ add_thread (ptid_t ptid)
   struct thread_info *result = add_thread_silent (ptid);
 
   if (print_thread_events)
-    printf_filtered (_("[New %s]\n"), target_pid_to_str (ptid));
+    printf_unfiltered (_("[New %s]\n"), target_pid_to_str (ptid));
   
   return result;
 }

-- 
Joel


  reply	other threads:[~2008-03-12 16:03 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-03-12  1:49 Pedro Alves
2008-03-12  3:01 ` Joel Brobecker
2008-03-12  3:13   ` Daniel Jacobowitz
2008-03-12 16:03     ` Joel Brobecker [this message]
2008-03-12 22:24       ` Pedro Alves
2008-03-12  3:27   ` Pedro Alves

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=20080312160306.GB3738@adacore.com \
    --to=brobecker@adacore.com \
    --cc=gdb-patches@sourceware.org \
    --cc=pedro@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