Hello. For quite some time I've been having problems attaching winedbg to a running process, for instance in the case of automatic invokation due to a crash. Direct invokation causes no problems and I also believe that my registry entries are all ok. My kernel is a standard 2.0.34 which otherwise has caused no problems and I use glibc 2.0.7 (yep, my system is oldish). I've traced the problem to this: debug_process() in server/debugger.c sets an error code which makes the debugger abort. To be more precise, this error code is set due to the call to get_thread_ip() ==> get_thread_context() which in turn calls: ptrace( PTRACE_GETREGS, pid, 0, ®s ) Now, this call fails for me with a EIO, so it seems like my system doesn't like PTRACE_GETREGS, at least according to the manpage? Did I miss anything, or can it really be the case? Are there any workarounds for this apart from just resetting the error code, which isn't very nice but gets the debugger going? How about a configure check or a error message for this? Should I prepare myself mentally for a system upgrade? ;-) Nicke -- -[ [EMAIL PROTECTED] ]- Seek simplicity, and distrust it. (A. Whitehead)
