Red Hat Bugzilla – Bug 456342
utrace: stop-attach-then-wait testcase FAILs
Last modified: 2011-02-02 13:52:22 EST
+++ This bug was initially created as a clone of Bug #454156 +++
Description of problem:
Process SIGSTOPs, debugger PTRACE_ATTACHes it, first WAITPID(,,0) returns
SIGSTOP but second WAITPID(,,0) returns SIG_0 (that one should be waiting).
Version-Release number of selected component (if applicable):
(but PASS on RHEL-4 kernel-smp-2.6.9-67.0.20.EL.x86_64)
Steps to Reproduce:
wget -O stop-attach-then-wait.c
gcc -o stop-attach-then-wait stop-attach-then-wait.c -Wall -ggdb2 -D_GNU_SOURCE;
./stop-attach-then-wait; echo $?
Upstream bugreport post:
This request was evaluated by Red Hat Product Management for
inclusion, but this component is not scheduled to be updated in
the current Red Hat Enterprise Linux release. If you would like
this request to be reviewed for the next minor release, ask your
support representative to set the next rhel-x.y flag to "?".
Unfortunately the previous automated notification about the
non-inclusion of this request in Red Hat Enterprise Linux 5.3 used
the wrong text template. It should have read: this request has been
reviewed by Product Management and is not planned for inclusion
in the current minor release of Red Hat Enterprise Linux.
If you would like this request to be reviewed for the next minor
release, ask your support representative to set the next rhel-x.y
flag to "?" or raise an exception.
It is a regression against RHEL-4.
I was unable to fix the Bug 456333 regressing issue 78487 as I was hitting this
Bug while coding it.
This bugzilla has Keywords: Regression.
Since no regressions are allowed between releases,
it is also being proposed as a blocker for this release.
Please resolve ASAP.
Pushing to RHEL 5.4, as this problem was not fixed for this release due to lower priority compared to other issues.
Updating PM score.
Well. I need to reserve the testing machine to verify.
But. I bet this was already fixed, and this bug duplicates
(In reply to comment #13)
> Well. I need to reserve the testing machine to verify.
> But. I bet this was already fixed, and this bug duplicates
> bz #481199
Yes, verified. Marking as duplicate.
*** This bug has been marked as a duplicate of bug 481199 ***