bug-gnu-emacs
[Top][All Lists]
Advanced

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

bug#9087: Crash reading from minibuffer with icomplete-mode


From: martin rudalics
Subject: bug#9087: Crash reading from minibuffer with icomplete-mode
Date: Fri, 06 Jan 2012 14:19:09 +0100

> Do you see the crash with the triggerbug.el recipe? It works (= crashes) for 
me.

For me too.  Can't do much with the backtrace, though :-(

martin


(gdb) run
Starting program: c:/emacs/quickfixes/bin/emacs.exe
[New thread 212.0x11c]
[New thread 212.0x404]
[New thread 212.0x784]
[New thread 212.0x748]
[New thread 212.0x278]
[New thread 212.0x664]
[New thread 212.0x174]
[New thread 212.0x1d8]
[New thread 212.0x59c]
gdb: unknown target exception 0xc0000029 at 0x7c95eb28

Program received signal ?, Unknown signal.
[Switching to thread 212.0x404]
0x7c95eb28 in ntdll!RtlInsertElementGenericTableAvl ()
   from C:\WINDOWS\system32\ntdll.dll
(gdb) bt
#0  0x7c95eb28 in ntdll!RtlInsertElementGenericTableAvl ()
   from C:\WINDOWS\system32\ntdll.dll
#1  0x77c05464 in msvcrt!_global_unwind2 ()
   from C:\WINDOWS\system32\msvcrt.dll
#2  0x77c06d8c in msvcrt!longjmp () from C:\WINDOWS\system32\msvcrt.dll
#3  0x0082ffe0 in ?? ()
#4  0x0101f938 in unwind_to_catch (catch=0x82ffe0, value=16906552)
    at eval.c:1323
Backtrace stopped: previous frame inner to this frame (corrupt stack?)

Lisp Backtrace:
"byte-code" (0x82e720)
"load" (0x82eef4)
"byte-compile-file" (0x82f0e0)
"let" (0x82f470)
"if" (0x82f600)
"let" (0x82f800)
"emacs-lisp-byte-compile-and-load-unconditionally" (0x82f994)
"call-interactively" (0x82fb94)
(gdb)





reply via email to

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