help-emacs-windows
[Top][All Lists]
Advanced

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

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


From: Troy Daniels
Subject: Re: [h-e-w] Emacs failing to start
Date: Thu, 18 Mar 2010 09:02:54 -0400

On Wed, Mar 17, 2010 at 4:17 PM, Eli Zaretskii <address@hidden> wrote:

This is a Cygwin build of (a rather old version of) GDB, whereas Emacs
is a native Windows program.  I would suggest to download the latest
GDB binary available from the MinGW site (at least 7.0), and try with
it.  It might show a more meaningful backtrace, even when Emacs is
stuck in a system call.


$ ./gdb --pid 1048
GNU gdb (GDB) 7.0.50.20100202
Copyright (C) 2010 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.  Type "show copying"
and "show warranty" for details.
This GDB was configured as "mingw32".
For bug reporting instructions, please see:
<http://www.gnu.org/software/gdb/bugs/>.
Attaching to process 1048
[New Thread 1048.0x31c]
[New Thread 1048.0x85c]
Reading symbols from C:\cygwin\home\udalrich\emacs\emacs-23.1\bin\emacs.exe...do
ne.
[Switching to Thread 1048.0x85c]
(gdb) info thread
* 2 Thread 1048.0x85c  0x7c90120f in ntdll!DbgUiConnectToDbg ()
   from C:\WINDOWS\system32\ntdll.dll
  1 Thread 1048.0x31c  0x7c90e514 in ntdll!LdrAccessResource ()
   from C:\WINDOWS\system32\ntdll.dll
(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.

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.)

Troy



 
> Any more ideas?

What happens if you run it under GDB to begin with -- does it also
hang when you type "run" at the GDB prompt?  If it does, perhaps step
through the `main' function and see where it hangs.


reply via email to

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