This is the mail archive of the
glibc-bugs@sourceware.org
mailing list for the glibc project.
[Bug libc/11901] __libc_message(do_abort = 1) will deadlock if called from malloc
- From: "walters at verbum dot org" <sourceware-bugzilla at sourceware dot org>
- To: glibc-bugs at sources dot redhat dot com
- Date: Wed, 2 Mar 2011 19:34:20 +0000
- Subject: [Bug libc/11901] __libc_message(do_abort = 1) will deadlock if called from malloc
- Auto-submitted: auto-generated
- References: <bug-11901-131@http.sourceware.org/bugzilla/>
http://sourceware.org/bugzilla/show_bug.cgi?id=11901
Colin <walters at verbum dot org> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |walters at verbum dot org
--- Comment #2 from Colin <walters at verbum dot org> 2011-03-02 19:34:03 UTC ---
A few thoughts on this:
* Potentially add another argument to _libc_fatal which says whether or not we
can use malloc?
* Will calling sbrk confuse malloc if the program happens to catch SIGABRT?
* Use alloca instead of malloc if the buffer is "small"? Actually, how about
always using alloca, and truncating the message to say 1024 characters?
* Why are there duplicate copies of libc_fatal.c in the tree?
--
Configure bugmail: http://sourceware.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.