This is the mail archive of the
mailing list for the glibc project.
Re: [PATCH roland/libc_fatal-no-syslog] Do not call syslog in __libc_message.
- From: Russ Allbery <rra at stanford dot edu>
- To: "GNU C. Library" <libc-alpha at sourceware dot org>
- Date: Wed, 20 Mar 2013 16:08:21 -0700
- Subject: Re: [PATCH roland/libc_fatal-no-syslog] Do not call syslog in __libc_message.
- References: <20130320215737 dot 556EA2C077 at topped-with-meat dot com> <871ub9emla dot fsf at windlord dot stanford dot edu> <20130320223517 dot 559AD2C07C at topped-with-meat dot com>
Roland McGrath <email@example.com> writes:
> I don't doubt that catching such cases is useful. libc is just not the
> right place to do it.
> If there is an actual crash, then you can set print-fatal-signals or you
> can install something fancy with core_pattern=|fancy-thing. There is no
> shortage of such fancy things around nowadays.
Ah, indeed, in fact when I went to go look at some examples, they were
caught by kernel logging, not something glibc was doing. Never mind,
carry on. :) Apologies for the noise.
Russ Allbery (firstname.lastname@example.org) <http://www.eyrie.org/~eagle/>