Re: gdb attach to process to produce stacktrace

["Hans Horn" <hannes at 2horns dot com>]

That's all I needed to know.
So in order for the process I'm attaching gdb to to terminate on its own I 
must not use anything that ends up in a windows dll.

In the mingw/msys sources (msys\rt\src\newlib\libc\sys\go32\sleep.c) I found 
a sleep impl (DJ Delorie, 1991) that emulates the sleep functionality using 
repeated time() calls.
no windows dll there - just what the doctor ordered.

thanks for all your help.
H.

"Dave Korn"  wrote in message 
027801c6dccb$91bb4980$a501a8c0@CAM.ARTIMI.COM">news:027801c6dccb$91bb4980$a501a8c0@CAM.ARTIMI.COM...
> On 20 September 2006 16:06, Hans Horn wrote:
>
>> The real question is as to why the parent process needs to go into a
>> while(1) loop in order to produce the desired trace.
>
>  Because then you're running in the program code, whereas in the sleep
> function you've ended up in a windows dll function and ...
>
>>> Note that if the process is stopped in a Windows DLL the stack trace
>>> will probably not be very informative.
>
>
>    cheers,
>      DaveK
> -- 
> Can't think of a witty .sigline today....
>
> 




--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Problem reports:       http://cygwin.com/problems.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/