This is the mail archive of the
libc-alpha@sourceware.org
mailing list for the glibc project.
Re: [PATCH] Do not print backtraces on fatal glibc errors
- From: "Dmitry V. Levin" <ldv at altlinux dot org>
- To: libc-alpha at sourceware dot org
- Date: Sat, 17 Aug 2019 00:56:44 +0300
- Subject: Re: [PATCH] Do not print backtraces on fatal glibc errors
- References: <875zmy2o8a.fsf@oldenburg2.str.redhat.com>
On Thu, Aug 15, 2019 at 10:00:21PM +0200, Florian Weimer wrote:
> If the process is in a bad state, we used to print backtraces in
> many cases. This is problematic because doing so could involve
> a lot of work, like loading libgcc_s using the dynamic linker,
> and this could itself be targeted by exploit writers. For example,
> if the crashing process was forked from a long-lived process, the
> addresses in the error message could be used to bypass ASLR.
>
> This commit completes the removal of backtrace printing from glibc.
> With the prevalence of external crash handlers, this functionality
> does not appear to be particular useful. The crash handler may also
> destroy useful information for debugging if coredumps are enabled.
s/particular useful/particularly useful/
--
ldv