This is the mail archive of the
gdb@sources.redhat.com
mailing list for the GDB project.
Re: Why does symfile.c use printf_filtered?
- From: Daniel Jacobowitz <drow at mvista dot com>
- To: Andrew Cagney <ac131313 at redhat dot com>
- Cc: "J. Johnston" <jjohnstn at redhat dot com>, gdb at sources dot redhat dot com
- Date: Fri, 24 Oct 2003 14:51:09 -0400
- Subject: Re: Why does symfile.c use printf_filtered?
- References: <3F95A56F.3090802@redhat.com> <3F996797.30205@redhat.com>
On Fri, Oct 24, 2003 at 01:55:35PM -0400, Andrew Cagney wrote:
> >Does anybody know why symfile.c uses printf_filtered()?
> >
> >This causes a couple of problems, most notably when you load a module with
> >a lot of shared library references. The messages for "Reading symbols
> >from"... inside symfile.c are printed filtered so eventually we end up
> >causing a page break. I do not think this information is worthy of
> >requiring user intervention.
> >
> >Would anybody have an objection to me changing to use printf_unfiltered()
> >in symfile.c?
>
> It certainly doesn't look right.
Which oesn't look right?
> Log messages are there to keep the user up-to-date on what GDB is doing
> (and confirm that GDB hasn't hung ...). Just like other such messages
> (thread notifications, hosted output from the remote) they should halt
"shouldn't"?
> GDB and hence shouldn't be paged.
>
> This is different to something like "info registers" where GDB has
> stopped, and the user expects to be able to read the entire response.
>
> enjoy,
> Andrew
>
>
>
--
Daniel Jacobowitz
MontaVista Software Debian GNU/Linux Developer