This is the mail archive of the
glibc-bugs@sources.redhat.com
mailing list for the glibc project.
[Bug nptl/914] pthread_atfork hangs thread after fork
- From: "mkwasigr at intercope dot com" <sourceware-bugzilla at sources dot redhat dot com>
- To: glibc-bugs at sources dot redhat dot com
- Date: 2 May 2005 12:36:15 -0000
- Subject: [Bug nptl/914] pthread_atfork hangs thread after fork
- References: <20050502122955.914.mkwasigr@intercope.com>
- Reply-to: sourceware-bugzilla at sources dot redhat dot com
------- Additional Comments From mkwasigr at intercope dot com 2005-05-02 12:36 -------
Created an attachment (id=473)
--> (http://sources.redhat.com/bugzilla/attachment.cgi?id=473&action=view)
Testcase for pthread_atfork() hang syptom on NPTL
Compile wit GCC using
cc -o thread_wait_atfork2 thread_wait_atfork2.c -lpthread
and run it using
./thread_wait_atfork2
Output is as follows:
MAIN (1115036517): Atfork handler installed.
MAIN (1115036517): Thread #1 started.
MAIN (1115036517): Calling Lock()...
Thread #0 (1115036517): restarting child
MAIN (1115036518): Calling Lock()...
MAIN (1115036519): Calling Lock()...
MAIN (1115036520): Calling Lock()...
MAIN (1115036521): Calling Lock()...
MAIN (1115036522): Calling Lock()...
MAIN (1115036523): Calling Lock()...
MAIN (1115036524): Calling Lock()...
MAIN (1115036525): Stop signal received, waiting for threads to end...
Expected behaviour would be that there are messages from MAIN and Thread
**EVERY** second.
--
http://sources.redhat.com/bugzilla/show_bug.cgi?id=914
------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.