Re: internal-error: insert_step_resume_breakpoint_at_sal

[Andrew Cagney <cagney at gnu dot org>]

Nick Roberts wrote:
>  > Tracking down these sorts of bugs is really important - it makes the 
>  > difference between a toy and a real debugger, and I think your efforts 
>  > have paid off :-)
>  > 
>  > With the log you provided I've been able to identify one bug - 
>  > back-to-back signals (where the inferior was receiving the next signal 
>  > just as the previous handler returned) would lead to a panic.
>  > 
>  > I'm about to commit a testcase and fix.
>
> With todays cvs (GNU gdb 6.3.50.20050126-cvs) I no longer get an internal
> error but everything hangs instead. I presume that it is GDB hanging and
> not Emacs, as Emacs does not hang at this place when its not running under
> debug (I'm only splitting a window).

"sick".  Is the testcase passing?

> However, I don't know how to get a backtrace as sending SIGINT (actually
> SIGSTOP with Emacs) interrupts the bottom level process (Emacs in this
> case). I can then interrupt the GDB being debugged, but presumably by then
> things have changed.

You can attach to gdb - $ gdb gdb <pid> - and then get a backtrace that way.

Anyway, same as before, lets look at a transcript (see the script 
command) with "set debug infrun 1" (and perhaphs also "set debug target 
1" - that one is really verbose).

Andrew