This is the mail archive of the
mailing list for the Cygwin project.
Re: fork failure?
Charles Wilson wrote:
> Charles Wilson wrote:
>> Which appears ok, as far as it goes. 'Course, something dies eventually
>> because I never do get to gpg-agent's "exec()" of pinvoke, after that fork.
> Well, bad news. In the kernel, the child gets right up to the return
> statement in fork(), returning 0. But it never reaches the line after
> the call to fork() in the user code.
> I note that procmon indicates that the child process exited with code
> -1073741783, which in hex is 0xc0000029. If that's an NTSTATUS value,
> then it means STATUS_INVALID_UNWIND_TARGET, but that might be a red herring.
Trashed stack during SEH unwind?
Might be able to get some useful info by running this under windbg and
intercepting the exception; even just an $eip to tell you where it's coming
from might be all the clue you needed.
Problem reports: http://cygwin.com/problems.html
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple