Description of problem: The current Fedora 9 kernel ptrace behavior does not correspond to the ideal one as decided on the utrace-devel mailing list. I am not aware any current practical debugger would be hit by it. Version-Release number of selected component (if applicable): kernel-2.6.25.4-30.fc9.x86_64 How reproducible: Always. Steps to Reproduce: wget -O step-jump-cont-strict.c 'http://sources.redhat.com/cgi-bin/cvsweb.cgi/~checkout~/tests/ptrace-tests/tests/step-jump-cont-strict.c?cvsroot=systemtap'; gcc -o step-jump-cont-strict step-jump-cont-strict.c -Wall -ggdb2 -D_GNU_SOURCE; ./step-jump-cont-strict; echo $? Actual results: ./step-jump-cont-strict: step-jump-cont-strict.c:365: test_singlestep (, instruction 7): Trap flag expected 1: found 0 1 Expected results: 0 Additional info: It was fixed by the Roland's patch: https://www.redhat.com/archives/utrace-devel/2008-April/msg00004.html but I did not find it in the Fedora kernels so far.
(In reply to comment #1) > Description of problem: > The current Fedora 9 kernel ptrace behavior does not correspond to the ideal one > as decided on the utrace-devel mailing list. > > Additional info: > It was fixed by the Roland's patch: > https://www.redhat.com/archives/utrace-devel/2008-April/msg00004.html > > but I did not find it in the Fedora kernels so far. That fix is in the current F9 2.6.27 kernel and the test passes on the F10 2.6.27 kernel, which has the same code.