Re: Why does symfile.c use printf_filtered?

[Andrew Cagney <ac131313@redhat.com>]

> 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.

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 
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