Mail Archives: cygwin/2004/12/30/21:52:55
On Thu, 30 Dec 2004 at 18:23:39 PM -0500, Christopher Faylor wrote:
>
> You missed step 5, apparently.
Well, actually, no, I didn't miss it, but step 5 did not appear to
yield any additional information. If I continue several times, I get:
> (gdb) run
> Starting program: /c/scratch/usr/bin/mount.exe
>
> Program received signal SIGSEGV, Segmentation fault.
> [Switching to thread 4168.0xc8c]
> 0x7c810858 in KERNEL32!CreateThread () from /c/WINDOWS/system32/kernel32.dll
> (gdb) c
> Continuing.
>
> Program received signal SIGSEGV, Segmentation fault.
> 0x7c810858 in KERNEL32!CreateThread () from /c/WINDOWS/system32/kernel32.dll
> (gdb) c
> Continuing.
>
> Program exited with code 030000000005.
I've tried instrumenting the code in dcrt0.cc to narrow down the
problem, without a lot of success. The thread that is faulting out
here is the one created by sigproc_init(). But if I rearrange the
code in dll_crt0_1(), then instead, I get a similar fault in a thread
created by fhandler_tty_master::init(). So the problem seems to be
with a precondition for successfully creating a new thread.
What thread gets created earlier than the wait_sig thread? I see that
gdb gives this thread id 3 but I can't tell what thread id 2 was; it
has exited (successfully?) before the trouble starts.
-- Dave
--
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/
- Raw text -