This is the mail archive of the
glibc-bugs@sourceware.org
mailing list for the glibc project.
[Bug libc/10638] system(3) does not catch its own SIGCHLD
- From: "phdm at macqel dot be" <sourceware-bugzilla at sourceware dot org>
- To: glibc-bugs at sources dot redhat dot com
- Date: 15 Sep 2009 11:35:50 -0000
- Subject: [Bug libc/10638] system(3) does not catch its own SIGCHLD
- References: <20090914131019.10638.phdm@macqel.be>
- Reply-to: sourceware-bugzilla at sourceware dot org
------- Additional Comments From phdm at macqel dot be 2009-09-15 11:35 -------
Sorry for wrong analysis. On sysv and AIX, one also get a SIGCHLD at the end of
system(3), but on sysv the wait call in the sigcld handler returns, so that the
program does not block. On AIX, the small example behaves as on linux, but my
real application does not block, while my application blocks on linux. I don't
know at the moment what makes the difference between AIX and linux behaviours in
my application.
--
http://sourceware.org/bugzilla/show_bug.cgi?id=10638
------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.