This is the mail archive of the
glibc-bugs@sourceware.org
mailing list for the glibc project.
[Bug malloc/770] possible deadlock on double-free logging
- From: "arequipeno at gmail dot com" <sourceware-bugzilla at sourceware dot org>
- To: glibc-bugs at sources dot redhat dot com
- Date: Tue, 17 Apr 2012 04:39:21 +0000
- Subject: [Bug malloc/770] possible deadlock on double-free logging
- Auto-submitted: auto-generated
- References: <bug-770-131@http.sourceware.org/bugzilla/>
http://sourceware.org/bugzilla/show_bug.cgi?id=770
--- Comment #13 from Ian Pilcher <arequipeno at gmail dot com> 2012-04-17 04:39:21 UTC ---
(In reply to comment #12)
> Ian, what you're hitting should have been fixed with commit id f8a3b5bf. The X
> backtrace is waiting on a lock in a malloc within __libc_message. The commit I
> mentioned replaces these malloc calls with mmap() calls to avoid getting
> tangled up in the arena locks.
Thanks Siddhesh!
Fortunately, I haven't seen this problem in quite a while. (I'd like to think
that the real problem in X has been fixed, but it seems more likely that my
system has changed enough that the race condition that causes the memory
corruption/detection isn't being triggered any more. Oh well.)
--
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.