From: Nick Roberts <nickrob@snap.net.nz>
To: Andrew Cagney <cagney@gnu.org>
Cc: gdb@sources.redhat.com
Subject: Re: internal-error: insert_step_resume_breakpoint_at_sal
Date: Wed, 26 Jan 2005 10:19:00 -0000 [thread overview]
Message-ID: <16887.27939.790997.257717@farnswood.snap.net.nz> (raw)
In-Reply-To: <41F56FCD.6090101@gnu.org>
> 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).
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.
Nick
next prev parent reply other threads:[~2005-01-26 10:19 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-11-24 4:02 Nick Roberts
2005-01-16 10:54 ` Nick Roberts
2005-01-18 18:59 ` Andrew Cagney
2005-01-18 21:53 ` Nick Roberts
2005-01-19 15:55 ` Andrew Cagney
2005-01-20 0:59 ` Nick Roberts
2005-01-20 10:23 ` Dave Korn
2005-01-20 10:58 ` Nick Roberts
2005-01-20 17:07 ` Andrew Cagney
2005-01-21 2:47 ` Nick Roberts
2005-01-24 21:59 ` Andrew Cagney
2005-01-26 10:19 ` Nick Roberts [this message]
2005-01-26 16:26 ` Andrew Cagney
2005-01-26 20:48 ` Nick Roberts
2005-01-26 21:39 ` Andrew Cagney
2005-01-27 1:02 ` Nick Roberts
2005-02-06 7:16 ` Andrew Cagney
2005-02-06 7:26 ` Andrew Cagney
2005-02-06 20:11 ` Nick Roberts
2005-02-08 16:57 ` Andrew Cagney
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=16887.27939.790997.257717@farnswood.snap.net.nz \
--to=nickrob@snap.net.nz \
--cc=cagney@gnu.org \
--cc=gdb@sources.redhat.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox