This is the mail archive of the
cygwin-developers
mailing list for the Cygwin project.
Re: Investigating a fork failure
- From: Jon TURNEY <jon dot turney at dronecode dot org dot uk>
- To: cygwin-developers at cygwin dot com
- Date: Mon, 24 Aug 2015 19:38:58 +0100
- Subject: Re: Investigating a fork failure
- Authentication-results: sourceware.org; auth=none
- References: <55DB2817 dot 5050903 at dronecode dot org dot uk> <20150824145612 dot GC13346 at calimero dot vinschen dot de>
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.