search for: ptrace_attach

Hi Keir, Ian, Today if we stop the guest for debugging using the gdbserver and then continue with the guest execution the PIT finds that the time has gone ahead and it missed to inject so many timer ticks, and it tries to inject all of those one by one. So after the gdb continue command the guest just handles the timer interrupts for a long time before it can do anything else. This patch

Hello, I am trying to get some more information about the following issue: # strace -p 2256 attach: ptrace(PTRACE_ATTACH, ...): Operation not permitted I am trying to trace an mdadm re-sync pid and I keep getting the above error. I have done some digging on google and forums, but have not had much luck. Redhat-release says CentOS release 5.5 (Final) uname: 2.6.18-194.32.1.el5 Any help would be great. -Eric ---...

https://bugzilla.samba.org/show_bug.cgi?id=2766 ------- Additional Comments From paul@debian.org 2005-06-02 08:47 ------- It seems to be looping in userspace (no system calls, hence strace doesn't show anything). Could you try ltrace instead of strace, that should show what library functions (if any) are being called which may help. -- Configure bugmail:

...at I've learned, this error is usually generated when init tries to continually respawn a process that dies immediately... but as to what process it could possible be I have no idea. I even tried to strace init (-p1), but apparently this is a forbidden operation: # strace -p1 attach: ptrace(PTRACE_ATTACH, ...): Operation not permitted That's a shame too, but at least I could see what init is trying to do. Any ideas? I'm just about stumped as to how to proceed at this point. Thanks in advance. -- ================================ David Halik System Administrator OIT-CSS Rutgers Universit...