This is the mail archive of the
mailing list for the Cygwin project.
Re: fork failure?
On Thu, Oct 15, 2009 at 01:07:10PM -0400, Charles Wilson wrote:
>Dave Korn wrote:
>> Charles Wilson wrote:
>>> the daemonized one. If I launch <cmd line> and then attach strace to
>>> the eventual pid of the daemonized process, it hangs (both strace and
>>> the process).
>> How about "gdb --attach PID"? Does that succeed? GDB has the advantage of
>> being a Cygwin rather than Win32 exe, which might make it work better when
>> taking hold of the running process.
>Well, since we don't support set fork-follow-child, I'm stuck in the
>parent (and I don't get far enough in the child to reach a 'sleep(N)'
>call, so the typical attach-after-fork approach won't work either). And
>the parent thinks everything is fine. I haven't tried linking against a
>debug-built DLL so as to step into the fork() call itself (hmm...why
>aren't the cygwin1.dbg files available for the 1.7.0-nn releases? They
>used to be shipped with 1.5.2x releases...)
...different person doing the release...
Problem reports: http://cygwin.com/problems.html
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple