This is the mail archive of the
gdb@sources.redhat.com
mailing list for the GDB project.
Why does symfile.c use printf_filtered?
- From: "J. Johnston" <jjohnstn at redhat dot com>
- To: gdb at sources dot redhat dot com
- Date: Tue, 21 Oct 2003 17:30:23 -0400
- Subject: Why does symfile.c use printf_filtered?
- Organization: Red Hat Inc.
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?
-- Jeff J.