This is the mail archive of the
glibc-bugs@sourceware.org
mailing list for the glibc project.
[Bug libc/10217] provide mechanism to examine assert/fatal messages from core file
- From: "fweimer at redhat dot com" <sourceware-bugzilla at sourceware dot org>
- To: glibc-bugs at sourceware dot org
- Date: Tue, 11 Jul 2017 18:27:54 +0000
- Subject: [Bug libc/10217] provide mechanism to examine assert/fatal messages from core file
- Auto-submitted: auto-generated
- References: <bug-10217-131@http.sourceware.org/bugzilla/>
https://sourceware.org/bugzilla/show_bug.cgi?id=10217
Florian Weimer <fweimer at redhat dot com> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |fweimer at redhat dot com
--- Comment #4 from Florian Weimer <fweimer at redhat dot com> ---
Could we use a bunch of volatile stack variables for this instead? I'm not
sure if it is such a good idea to call malloc (via asprintf) from assert.
Ideally, assert should be async-signal-safe as a quality-of-implementation
matter.
--
You are receiving this mail because:
You are on the CC list for the bug.