Re: On Cygwin: bootstrap hangs when compiling lisp files...

[Ping Liang]

I was able to take the latter approach and it worked.  Here is the traceback

 

Loaded symbols for /cygdrive/c/WINDOWS/system32/ntdll.dll
Loaded symbols for /cygdrive/c/WINDOWS/system32/kernel32.dll
Loaded symbols for /usr/bin/cygncurses-8.dll
Loaded symbols for /usr/bin/cygwin1.dll
Loaded symbols for /cygdrive/c/WINDOWS/system32/advapi32.dll
Loaded symbols for /cygdrive/c/WINDOWS/system32/rpcrt4.dll
Loaded symbols for /cygdrive/c/WINDOWS/system32/ws2_32.dll
Loaded symbols for /cygdrive/c/WINDOWS/system32/msvcrt.dll
Loaded symbols for /cygdrive/c/WINDOWS/system32/ws2help.dll
Loaded symbols for /cygdrive/c/WINDOWS/System32/mswsock.dll
Loaded symbols for /cygdrive/c/WINDOWS/system32/dnsapi.dll
Loaded symbols for /cygdrive/c/WINDOWS/System32/winrnr.dll
Loaded symbols for /cygdrive/c/WINDOWS/system32/wldap32.dll
Loaded symbols for /cygdrive/c/WINDOWS/system32/rasadhlp.dll
[Switching to thread 3340.0xe18]
(gdb) bt
#0  0x7c901231 in ntdll!DbgUiConnectToDbg ()
   from /cygdrive/c/WINDOWS/system32/ntdll.dll
#1  0x7c9507a8 in ntdll!KiIntSystemCall ()
   from /cygdrive/c/WINDOWS/system32/ntdll.dll
#2  0x00000005 in ?? ()
#3  0x00000004 in ?? ()
#4  0x00000001 in ?? ()
#5  0x1873ffd0 in ?? ()
#6  0x00000246 in ?? ()
#7  0xffffffff in ?? ()
#8  0x7c90ee18 in strchr () from /cygdrive/c/WINDOWS/system32/ntdll.dll
#9  0x7c9507c8 in ntdll!KiIntSystemCall ()
   from /cygdrive/c/WINDOWS/system32/ntdll.dll
#10 0x00000000 in ?? ()
(gdb)

 

On 8/9/06, Eli Zaretskii <address@hidden> wrote:

> Date: Wed, 9 Aug 2006 22:50:44 -0400
> From: "Ping Liang" < address@hidden>
>
> Sorry it takes this long to reply.  When I ran it under gdb, control-c
> wouldn't break it.  I ended up getting out by killing the process itself
> (took 40% cpu).  So I couldn't do bt.
>
> Any other hint, please?


There's no way to debug this except if we can interrupt Emacs when
it's looping.  I don't know how to do that, since I don't use Cygwin.
Please ask on the Cygwin mailing list how to interrupt a Cygwin
program when it runs under GDB; perhaps you can use the `kill'
command, if you have its Cygwin port installed.

Another possibility is to run Emacs outside GDB, and when it starts
looping invoke GDB as "gdb -p PID", where PID is the Emacs process ID
number.  If that succeeds, it will stop Emacs, and you should then be
able to do a backtrace.

And please don't remove the mailing list from the CC header, I'd like
to keep this discussion on the list so that others could contribute
ideas.