Hi,
We experiment the same issue. It is related to this fix:
linux-2.6-misc-ptrace-fix-exec-report.patch and the related bugzilla:
https://bugzilla.redhat.com/show_bug.cgi?id=455060
We patched the ptrace.c with this:
***
I'm not sure if this is the place for this, but:
I have an x86_64 machine that gets an immediate SIGSEGV when ptracing anything:
[r...@dl360g6gs1 kernel-2.6.18]# strace true
execve(/bin/true, [true], [/* 28 vars */]) = 0
--- SIGSEGV (Segmentation fault) @ 0 (0) ---
+++ killed by SIGSEGV +++
I
On Fri, Feb 26, 2010 at 12:33 PM, Roland McGrath rol...@redhat.com wrote:
If you are using actual RHEL5, you can go through your normal support
channels for help on that. I don't know off hand of anybody who wants to
help you with support for using RHEL5 kernel source built with a set of
But I'm happy to have tracked it down to the utrace-based ptrace
emulation, and was mostly just interested in knowing if preempt and
utrace are fundamentally incompatible on x86_64, or something like
that. I'll fight through the 2.6.18-164 issues instead, since the
ptrace problem doesn't seem
