Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Daniel Jacobowitz <drow@mvista.com>
To: "J. Johnston" <jjohnstn@redhat.com>
Cc: gdb-patches@sources.redhat.com, jimb@redhat.com
Subject: Re: RFA: switch to printf_unfiltered in symfile.c
Date: Tue, 28 Oct 2003 04:30:00 -0000	[thread overview]
Message-ID: <20031028043039.GA27446@nevyn.them.org> (raw)
In-Reply-To: <3F96CF9A.9080003@redhat.com>

On Wed, Oct 22, 2003 at 02:42:34PM -0400, J. Johnston wrote:
> The following patch switches over the majority of the printfs in symfile.c 
> to use printf_unfiltered.  This fixes a problem whereby if you attach to a 
> process that has a lot of dynamic library references, you will get page 
> breaks as it displays loading symbols messages.
> 
> I purposely left printf_filtered for info_ext_lang_command(), and 
> list_overlays_command() as I felt that a user may want to examine the 
> output and this should allow paging if necessary.
> 
> Ok to commit?
> 
> -- Jeff J.
> 
> 2003-10-22  Jeff Johnston  <jjohnstn@redhat.com>
> 
> 	* symfile.c (symbol_file_add_with_addrs_or_offsets): Switch to use
> 	printf_unfiltered instead of printf_filtered for output messages.
> 	(add_symbol_file_command): Ditto.
> 	(reread_symbols): Ditto.
> 	(overlay_auto_command): Ditto.
> 	(overlay_manual_command): Ditto.
> 	(overlay_off_command): Ditto.

Do any of our symtab maintainers have a comment on this patch?  I
vaguely remember that you agreed with it on gdb@, Jim?


-- 
Daniel Jacobowitz
MontaVista Software                         Debian GNU/Linux Developer


  reply	other threads:[~2003-10-28  4:30 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-10-22 18:42 J. Johnston
2003-10-28  4:30 ` Daniel Jacobowitz [this message]
2003-10-28 16:08   ` Elena Zannoni
2003-10-28 17:09     ` J. Johnston
2003-10-28 18:17     ` Jim Blandy

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=20031028043039.GA27446@nevyn.them.org \
    --to=drow@mvista.com \
    --cc=gdb-patches@sources.redhat.com \
    --cc=jimb@redhat.com \
    --cc=jjohnstn@redhat.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