[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [h-e-w] Emacs failing to start

From: Eli Zaretskii
Subject: Re: [h-e-w] Emacs failing to start
Date: Thu, 18 Mar 2010 09:43:35 -0400

> From: Troy Daniels <address@hidden>
> Date: Thu, 18 Mar 2010 09:02:54 -0400
> Cc: address@hidden
> (gdb) thread 1
> [Switching to thread 1 (Thread 1048.0x31c)]#0  0x7c90e514 in 
> ntdll!LdrAccessReso
> urce () from C:\WINDOWS\system32\ntdll.dll
> (gdb) bt
> #0  0x7c90e514 in ntdll!LdrAccessResource ()
>    from C:\WINDOWS\system32\ntdll.dll
> #1  0x7c90df5a in ntdll!ZwWaitForSingleObject ()
>    from C:\WINDOWS\system32\ntdll.dll
> #2  0x7c8025db in WaitForSingleObjectEx ()
>    from C:\WINDOWS\system32\kernel32.dll
> #3  0x00000749 in ?? ()
> #4  0x00000000 in ?? ()
> I don't think that's much more useful.

No, it isn't.

> If I run it from gdb, it hangs.  C-c will give me a gdb prompt.  From there,
> where gives me the same stack trace as above.  I suspect the ?? in the stack
> trace are due to emacs not being compiled with debug info.  (I assume that's
> how the standard distribution is built.)

I didn't realize this binary was not built by yourself.  But I think
you are wrong assuming that it does not have debug info:

> Reading symbols from 
> C:\cygwin\home\udalrich\emacs\emacs-23.1\bin\emacs.exe...done.

This messages means that GDB did find the symbols.

Can you try single-stepping (with `next') through the `main' function?
If it works, it means you do have debug symbols in the binary, and
then please see which call hangs.

reply via email to

[Prev in Thread] Current Thread [Next in Thread]