From: Mark Kettenis <kettenis@gnu.org>
To: schwab@suse.de
Cc: gdb@sources.redhat.com
Subject: Re: infrun.c:2642: internal-error: insert_step_resume_breakpoint_at_sal: Assertion `step_resume_breakpoint == NULL' failed dot
Date: Sat, 30 Oct 2004 17:27:00 -0000 [thread overview]
Message-ID: <200410291752.i9THq3JQ001379@elgar.sibelius.xs4all.nl> (raw)
In-Reply-To: <je3bzxwnu6.fsf@sykes.suse.de> (message from Andreas Schwab on Fri, 29 Oct 2004 17:22:57 +0200)
From: Andreas Schwab <schwab@suse.de>
Date: Fri, 29 Oct 2004 17:22:57 +0200
I'm getting this assertion failure on ia64-linux when stepping after a
breakpoint with a signal also being delivered. Both calls to
insert_step_resume_breakpoint_at_sal are coming from the two calls to
insert_step_resume_breakpoint_at_frame in handle_inferior_event. In both
calls the actual address where the breakpoint is to be set is the same. I
haven't been able to come up with a small test case, this happens while
debugging Emacs.
I'm seeing the same problem on NetBSD/amd64 in the regular testsuite
(sigstep.exp). Haven't found the time yet to look into it though.
Mark
prev parent reply other threads:[~2004-10-29 17:52 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-10-29 19:32 infrun.c:2642: internal-error: insert_step_resume_breakpoint_at_sal: Assertion `step_resume_breakpoint == NULL' failed Andreas Schwab
2004-10-30 14:54 ` Andrew Cagney
2004-10-30 17:47 ` Andreas Schwab
2004-10-30 19:48 ` Andrew Cagney
2004-10-31 16:18 ` Andreas Schwab
2004-10-31 19:12 ` Andrew Cagney
[not found] ` <je8y9okn2b.fsf@sykes.suse.de>
2004-11-01 18:05 ` Andrew Cagney
2004-11-02 15:25 ` Andreas Schwab
2005-01-26 21:10 ` Andrew Cagney
2005-01-27 15:25 ` Andreas Schwab
2004-10-30 17:27 ` Mark Kettenis [this message]
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=200410291752.i9THq3JQ001379@elgar.sibelius.xs4all.nl \
--to=kettenis@gnu.org \
--cc=gdb@sources.redhat.com \
--cc=schwab@suse.de \
/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