Investigating a fork failure

Corinna Vinschen corinna-cygwin@cygwin.com
Mon Aug 24 18:54:00 GMT 2015


On Aug 24 19:38, Jon TURNEY wrote:
> On 24/08/2015 15:56, Corinna Vinschen wrote:
> >On Aug 24 15:20, Jon TURNEY wrote:
> >The backtrace looks weird.  Did you run this with a Cygwin DLL built
> >without optimization?  That might be helpful.
> 
> I ran this using 2.2.0-1
> 
> I'm afraid windbg doesn't do a very good job symbolicating the backtrace
> through cygwin1.dll, as it only has access to the exported symbols.
> 
> Feeding the RAs into addr2line gives:
> 
> >0x00000001800ab085 fhandler_socket::fixup_after_fork(void*) fhandler_socket.cc:842
> >0x000000018006d8b7 dtable::fixup_after_exec()               dtable.cc:895
> >0x00000001800469d0 child_info_spawn::handle_spawn()         dcrt0.cc:688
> >0x000000018004897c dll_crt0_0()                             dcrt0.cc:797
> >0x00000001800c62e9 dll_entry                                init.cc:85
> 
> which hopefully looks a bit more normal.

You may want to debug what happens in fdsock.  Read the comment in
there, it should help to understand what's going on.


Corinna

-- 
Corinna Vinschen                  Please, send mails regarding Cygwin to
Cygwin Maintainer                 cygwin AT cygwin DOT com
Red Hat
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 819 bytes
Desc: not available
URL: <http://cygwin.com/pipermail/cygwin-developers/attachments/20150824/087b784c/attachment.sig>


More information about the Cygwin-developers mailing list