--- Begin Message ---
Subject: |
24.3.50; emacs_backtrace.txt |
Date: |
Sat, 6 Jul 2013 19:22:05 -0700 (PDT) |
Backtrace:
0x011ee099
0x011ee10b
0x010db39c
0x010ff435
0x010ff410
0x010ff469
0x010011e6
0x770a74db
0x77069ec1
In GNU Emacs 24.3.50.1 (i686-pc-mingw32)
of 2013-07-01 on LEG570
Bzr revision: 113246 address@hidden
Windowing system distributor `Microsoft Corp.', version 6.1.7601
Configured using:
`configure --prefix=/c/usr --enable-checking CFLAGS='-O0 -g3'
CPPFLAGS='-DGLYPH_DEBUG=1 -I/c/usr/include''
--- End Message ---
--- Begin Message ---
Subject: |
Re: bug#14809: 24.3.50; emacs_backtrace.txt |
Date: |
Sun, 07 Jul 2013 23:01:34 +0300 |
> Date: Sun, 7 Jul 2013 21:53:36 +0200
> From: Dani Moncayo <address@hidden>
> Cc: address@hidden
>
> Translated backtrace:
>
> w32_backtrace at w32fns.c:7757
> emacs_abort at w32fns.c:7789
> terminate_due_to_signal at emacs.c:350
> handle_fatal_signal at sysdep.c:1649
> deliver_thread_signal at sysdep.c:1625
> deliver_fatal_thread_signal at sysdep.c:1661
> ?? at crt1.c:0
Thanks. This is some kind of fatal exception that was caught by the
top-level exception handler set up by the startup code. There's
nothing that can be done with this kind of problems, except by
catching them when Emacs is run under GDB.
Closing.
--- End Message ---