This is the mail archive of the
glibc-bugs@sourceware.org
mailing list for the glibc project.
[Bug libc/13699] Hang in __lll_lock_wait_private after fork and realloc.
- From: "fweimer at redhat dot com" <sourceware-bugzilla at sourceware dot org>
- To: glibc-bugs at sourceware dot org
- Date: Tue, 05 Jan 2016 12:14:41 +0000
- Subject: [Bug libc/13699] Hang in __lll_lock_wait_private after fork and realloc.
- Auto-submitted: auto-generated
- References: <bug-13699-131 at http dot sourceware dot org/bugzilla/>
https://sourceware.org/bugzilla/show_bug.cgi?id=13699
Florian Weimer <fweimer at redhat dot com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|REOPENED |RESOLVED
CC| |fweimer at redhat dot com
Resolution|--- |FIXED
Target Milestone|--- |2.15.1
--- Comment #6 from Florian Weimer <fweimer at redhat dot com> ---
(In reply to Ionut Ceausu from comment #5)
> Problem is still reproducible on GLIBC2.17/ubunt 13.04. Attached is the
> source code to reproduce the problem.
> Stack is the following one
> __lll_lock_wait_private() at lowlevellock.S:95 0x7ffff73e3d7b
> _L_lock_697() at 0x7ffff73d0af4
> __GI___vsyslog_chk() at syslog.c:258 0x7ffff73d0524
> __syslog() at syslog.c:117 0x7ffff73d099f
This is a different problem. I filed it as bug 19429.
--
You are receiving this mail because:
You are on the CC list for the bug.