From: Daniel Jacobowitz <drow@false.org>
To: Joel Brobecker <brobecker@adacore.com>
Cc: Pedro Alves <pedro@codesourcery.com>, gdb-patches@sourceware.org
Subject: Re: Don't paginate "new thread" events
Date: Wed, 12 Mar 2008 03:13:00 -0000 [thread overview]
Message-ID: <20080312031329.GA12967@caradoc.them.org> (raw)
In-Reply-To: <20080312030129.GA3738@adacore.com>
On Tue, Mar 11, 2008 at 08:01:29PM -0700, Joel Brobecker wrote:
> > New thread events printing ("New Thread 0x40077950 (LWP 13229)]") was
> > recently centralised in add_thread. Unfortunatelly it brought with
> > it a behaviour change. Before, we wouldn't paginate when these
> > events filled the terminal screen, and now we do.
>
> Actually, I think it's a little more complicated than that. I had
> a second look at the patch, and the routines that were used to print
> the event notifications were either "printf_filtered" or "ui_out_text"
> (which in CLI mode results in a printf_filtered).
The one most frequently encountered, in linux-thread-db.c,
was already unfiltered for this very reason.
--
Daniel Jacobowitz
CodeSourcery
next prev parent reply other threads:[~2008-03-12 3:13 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 [this message]
2008-03-12 16:03 ` Joel Brobecker
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=20080312031329.GA12967@caradoc.them.org \
--to=drow@false.org \
--cc=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