bug#17753: Cygwin emacs-X11 core dump

[Eli Zaretskii]

> Date: Wed, 17 Sep 2014 11:45:19 +0200
> From: Markus Hoenicka <markus.hoenicka@mhoenicka.de>
> Cc: 17753@debbugs.gnu.org, Eli Zaretskii <eliz@gnu.org>
> 
> Thread 2 (Thread 5044.0x13f4):
> #0  0x000000007770131a in ntdll!ZwReadFile ()
>     from /cygdrive/c/WINDOWS/system32/ntdll.dll
> #1  0x000007fefd6d1a7a in ReadFile ()
>     from /cygdrive/c/WINDOWS/system32/KERNELBASE.dll
> #2  0x000000000042ce00 in ?? ()
> #3  0x0000000100587330 in schedule_atimer ()
>      at /usr/src/debug/emacs-24.3.93-1/src/atimer.c:337
> #4  0x00000001802df9f8 in ?? () from /usr/bin/cygwin1.dll
> #5  0x0000000000000000 in ?? ()
> 
> Thread 1 (Thread 5044.0x13ac):
> #0  0x00000005e20450f0 in cygfontconfig-1!FcObjectLookupOtherTypeById ()
>     from /usr/bin/cygfontconfig-1.dll
> #1  0x00000005e20458ed in cygfontconfig-1!FcPatternObjectFindElt ()
>     from /usr/bin/cygfontconfig-1.dll
> #2  0x0000000000000001 in ?? ()
> #3  0x0000000000000003 in ?? ()
> #4  0x0000000000423c90 in ?? ()
> #5  0x00000006034f3e45 in ?? ()
> #6  0x0000000000000000 in ?? ()

It looks like your GDB is still unable to read the symbolic debug info
for some reason.

Anyway, one thing that strikes me (and is consistent across all your
reports until now) is that atimer.c functions are run from a separate
thread, not the main thread (which is Thread 1).  Ken, is this normal
in the Cygwin-w32 build?