public inbox for glibc-bugs@sourceware.org help / color / mirror / Atom feed
From: "gf at unixsol dot org" <sourceware-bugzilla@sourceware.org> To: glibc-bugs@sources.redhat.com Subject: [Bug libc/13699] New: Hang in __lll_lock_wait_private after fork and realloc. Date: Thu, 16 Feb 2012 11:38:00 -0000 [thread overview] Message-ID: <bug-13699-131@http.sourceware.org/bugzilla/> (raw) http://sourceware.org/bugzilla/show_bug.cgi?id=13699 Bug #: 13699 Summary: Hang in __lll_lock_wait_private after fork and realloc. Product: glibc Version: 2.13 Status: NEW Severity: normal Priority: P2 Component: libc AssignedTo: drepper.fsp@gmail.com ReportedBy: gf@unixsol.org Classification: Unclassified I'm using glibc 2.13 from Slackware 13.37 on x86-64. One of our local programs hangs from time to time and I have kill -9 it. Today I was able to get core file and get the following back trace. #0 0x00007f3118abfa8e in __lll_lock_wait_private () from /lib64/libc.so.6 #1 0x00007f3118a49c75 in _L_lock_12271 () from /lib64/libc.so.6 #2 0x00007f3118a47efd in realloc () from /lib64/libc.so.6 #3 0x00007f3118a3b633 in vasprintf () from /lib64/libc.so.6 #4 0x00007f3118a1c238 in asprintf () from /lib64/libc.so.6 #5 0x00007f31189f7863 in __assert_fail () from /lib64/libc.so.6 #6 0x00007f3118d76366 in __reclaim_stacks () from /lib64/libpthread.so.0 #7 0x00007f3118a78a36 in fork () from /lib64/libc.so.6 #8 0x000000000040672d in do_notify (in=<value optimized out>) at lib/inotify.c:39 #9 0x00007f3118d76d6b in start_thread () from /lib64/libpthread.so.0 #10 0x00007f3118ab045d in clone () from /lib64/libc.so.6 The program uses about 4G memory on machine with 16G and and 2.6.38.7 kernel. The notify function looks like this: https://github.com/gfto/tsdecrypt/blob/master/notify.c#L46 I understand the problem is some kind of malloc related deadlock but I have no idea how to avoid or work around it. There is currently glibc 2.14.1 in slackware-current, will updating to this version fix the problem? -- 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.
next reply other threads:[~2012-02-16 11:38 UTC|newest] Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top 2012-02-16 11:38 gf at unixsol dot org [this message] 2012-02-16 16:10 ` [Bug libc/13699] " law at redhat dot com 2012-10-03 18:29 ` siddhesh at redhat dot com 2012-10-04 15:58 ` gf at unixsol dot org 2014-06-26 15:22 ` fweimer at redhat dot com 2014-07-17 10:19 ` ionut.ceausu at gmail dot com 2014-07-17 10:21 ` ionut.ceausu at gmail dot com
Reply instructions: You may reply publicly to this message via plain-text email using any one of the following methods: * Save the following mbox file, import it into your mail client, and reply-to-all from there: mbox Avoid top-posting and favor interleaved quoting: https://en.wikipedia.org/wiki/Posting_style#Interleaved_style * Reply using the --to, --cc, and --in-reply-to switches of git-send-email(1): git send-email \ --in-reply-to=bug-13699-131@http.sourceware.org/bugzilla/ \ --to=sourceware-bugzilla@sourceware.org \ --cc=glibc-bugs@sources.redhat.com \ /path/to/YOUR_REPLY https://kernel.org/pub/software/scm/git/docs/git-send-email.html * If your mail client supports setting the In-Reply-To header via mailto: links, try the mailto: linkBe sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox; as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).