This is the mail archive of the
frysk-bugzilla@sourceware.org
mailing list for the frysk project.
[Bug general/3639] fc6: testTerminateKillKILL(frysk.proc.TestTaskTerminateObserver)
- From: "roland at gnu dot org" <sourceware-bugzilla at sourceware dot org>
- To: frysk-bugzilla at sourceware dot org
- Date: 26 Mar 2007 20:52:19 -0000
- Subject: [Bug general/3639] fc6: testTerminateKillKILL(frysk.proc.TestTaskTerminateObserver)
- References: <20061204180758.3639.cmoller@redhat.com>
- Reply-to: sourceware-bugzilla at sourceware dot org
------- Additional Comments From roland at gnu dot org 2007-03-26 21:52 -------
I don't know what's going on in the frysk world, but a couple things from the
kernel side might be relevant.
First is that for death by SIGKILL you may well not see any EXIT event
(WIFSTOPPED, SIGTRAP|PTRACE_EVENT_EXIT<<16).
You will see the death event (WIFSIGNALED) for sure except possibly in the case
of multi-threaded exec by a non-leader thread (when you won't see a report from
the old leader, but the exec'ing thread will change its PID to the leader's).
Second is there is a rare race bug in kernels before the recent test kernels,
that can produce a bogus wait status value. The bogus value will be a
WIFSTOPPED with WSTOPSIG 0 or some high bits set. This is a very unlikely race.
Also, it doesn't produce a WIFEXITED value in the bug case, so it doesn't seem
likely to be relevant to what you are seeing.
Nothing comes to mind with a bogus status of 0x8000. An _exit(128) produces
that status.
--
http://sourceware.org/bugzilla/show_bug.cgi?id=3639
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.