bug-gdb
[Top][All Lists]
Advanced

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

Bug in tracing frames


From: Richard Stallman
Subject: Bug in tracing frames
Date: Tue, 07 Jan 2014 11:53:24 -0500

[[[ To any NSA and FBI agents reading my email: please consider    ]]]
[[[ whether defending the US Constitution against all enemies,     ]]]
[[[ foreign or domestic, requires you to follow Snowden's example. ]]]

In gdb 7.01-debian, Emacs got into an infloop and I typed C-g C-g to
get back to GDB.  I got the following incomplete backtrace.  Evidently
GDB is unable to trace the stack back properly from the signal
handler.

This is on the Lemote Yeeloong.

Please ack receipt of this message.


#0  0x76a4d3c4 in kill () from /lib/libc.so.6
#1  0x00657004 in sys_suspend () at sysdep.c:450
#2  0x0063fcf8 in handle_interrupt (in_signal_handler=true) at keyboard.c:10318
#3  0x0063fb18 in handle_interrupt_signal (sig=2) at keyboard.c:10259
#4  0x006599b0 in deliver_process_signal (sig=2, 
    handler=0x63fa78 <handle_interrupt_signal>) at sysdep.c:1568
#5  0x0063fb74 in deliver_interrupt_signal (sig=2) at keyboard.c:10266
#6  <signal handler called>
#7  0x00000000 in ?? ()
#8  0x00000000 in ?? ()

Lisp Backtrace:
"get-text-property" (0x7fff09e8)
"font-lock-extend-jit-lock-region-after-change" (0x7fff0dbc)
"run-hook-with-args" (0x7fff0db8)
"jit-lock-after-change" (0x7fff1144)
"replace-match" (0x7fff1348)
"grep-filter" (0x7fff1698)
"run-hooks" (0x7fff1710)
"compilation-filter" (0x7fff19dc)

-- 
Dr Richard Stallman
President, Free Software Foundation
51 Franklin St
Boston MA 02110
USA
www.fsf.org  www.gnu.org
Skype: No way! That's nonfree (freedom-denying) software.
  Use Ekiga or an ordinary phone call.




reply via email to

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