This is the mail archive of the libc-hacker@sources.redhat.com mailing list for the glibc project.
Note that libc-hacker is a closed list. You may look at the archives of this list, but subscription and posting are not open.
Index Nav: | [Date Index] [Subject Index] [Author Index] [Thread Index] | |
---|---|---|
Message Nav: | [Date Prev] [Date Next] | [Thread Prev] [Thread Next] |
Other format: | [Raw text] |
On Thu, Oct 31, 2002 at 02:50:28PM -0500, Jes Sorensen wrote: > Hi > > We are chasing a problem on Linux/mips with glibc-2.2.x, which I am not > sure whether is a kernel bug or a libc bug. We haven't been able to > reproduce it under Linux/x86 or Linux/ia64 so far though. > > Basically what seems to be happening is the following, a task is > spawned from fork(), the child sends some signals to the parent after > which it exits. > > The parent exits before the signals arrives and a signal is delivered > some time after reaching exit(). As the signal handler is using > printf() we get an explosion since the file descriptor seems to be > gone (munmap()). > > My question is as follows: Is one required to wait for signal delivery > in the parent before exiting or unregister the signal handlers? or is > it a genuine bug? > > Any suggestions? > A testcase? H.J.
Index Nav: | [Date Index] [Subject Index] [Author Index] [Thread Index] | |
---|---|---|
Message Nav: | [Date Prev] [Date Next] | [Thread Prev] [Thread Next] |