[prev in list] [next in list] [prev in thread] [next in thread] 

List:       gdb-bugs
Subject:    Re: Bug in tracing frames
From:       Sergio Durigan Junior <sergiodj () sergiodj ! net>
Date:       2014-01-07 17:06:58
Message-ID: m3ob3nzpot.fsf () sergiodj ! net
[Download RAW message or body]

On Tuesday, January 07 2014, Richard Stallman wrote:

> [[[ 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 ?? ()

Thanks for the report.

I believe there are two bugs in our bugzilla which are related to this
issue:

<https://sourceware.org/bugzilla/show_bug.cgi?id=14506>

<https://sourceware.org/bugzilla/show_bug.cgi?id=11348>

AFAIR, there has been no attempt to fix those yet.

-- 
Sergio


[prev in list] [next in list] [prev in thread] [next in thread]