This is the mail archive of the
glibc-bugs@sourceware.org
mailing list for the glibc project.
[Bug libc/20061] backtrace() is not async signal safe (malloc in _dl_load_cache_lookup)
- From: "dx at dxzone dot com.ar" <sourceware-bugzilla at sourceware dot org>
- To: glibc-bugs at sourceware dot org
- Date: Wed, 11 May 2016 18:37:00 +0000
- Subject: [Bug libc/20061] backtrace() is not async signal safe (malloc in _dl_load_cache_lookup)
- Auto-submitted: auto-generated
- References: <bug-20061-131 at http dot sourceware dot org/bugzilla/>
https://sourceware.org/bugzilla/show_bug.cgi?id=20061
--- Comment #2 from dx <dx at dxzone dot com.ar> ---
Thanks for the reply, but where does it say that? The man page I have here says
nothing about this. http://linux.die.net/man/3/backtrace
There's a slight indirect implication of backtrace_symbols_fd() being more
async-signal-safe than backtrace_symbols(), but no direct mention of that and
nothing about backtrace() itself.
Does this mean we're not supposed to use backtrace() from segfault handlers at
all?
--
You are receiving this mail because:
You are on the CC list for the bug.