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: Eli Zaretskii <eliz at elta dot co dot il>
- To: "J. Johnston" <jjohnstn at redhat dot com>
- Cc: gdb at sources dot redhat dot com
- Date: 22 Oct 2003 08:17:22 +0200
- Subject: Re: Why does symfile.c use printf_filtered?
- References: <3F95A56F.3090802@redhat.com>
- Reply-to: Eli Zaretskii <eliz at elta dot co dot il>
> Date: Tue, 21 Oct 2003 17:30:23 -0400
> From: "J. Johnston" <jjohnstn@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.
Unless there's some important situation where this is necessary, it
does seem silly to use printf_filtered in this case.