This is the mail archive of the gdb@sources.redhat.com mailing list for the GDB project.

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]
Other format:	[Raw text]

Re: infrun.c:2642: internal-error: insert_step_resume_breakpoint_at_sal:Assertion `step_resume_breakpoint == NULL' failed.

From: Andrew Cagney <cagney at gnu dot org>
To: Andreas Schwab <schwab at suse dot de>
Cc: Andrew Cagney <ac131313 at redhat dot com>, gdb at sources dot redhat dot com, Nick Roberts <nickrob at snap dot net dot nz>
Date: Wed, 26 Jan 2005 16:09:49 -0500
Subject: Re: infrun.c:2642: internal-error: insert_step_resume_breakpoint_at_sal:Assertion `step_resume_breakpoint == NULL' failed.
References: <je3bzxwnu6.fsf@sykes.suse.de> <418280F3.1090502@redhat.com> <jefz3xwc9w.fsf@sykes.suse.de> <41839D0D.8070700@gnu.org> <jehdocktig.fsf@sykes.suse.de> <4183C57F.2020502@gnu.org> <je8y9okn2b.fsf@sykes.suse.de> <41867AC4.5080005@redhat.com> <jefz3sth3n.fsf@sykes.suse.de>

Andreas Schwab wrote:

Andrew Cagney <ac131313@redhat.com> writes:
No, the above does that (but with SIGALRM).  Are there multiple signals
pending?
Doesn't seem so.
Time to post (gdb) set debug target 1 ; run.
It's attached.

Andreas.

Andreas,

I've fixed one bug related to back-to-back signals that would cause this internal error (testsuite gdb.base/sigrepeat.exp). Can you re-run your senario? Nick, who encountered similar problems, found his problem moved :-/

Andrew

Follow-Ups:
- Re: infrun.c:2642: internal-error:insert_step_resume_breakpoint_at_sal: Assertion `step_resume_breakpoint ==NULL' failed.
  - From: Andreas Schwab

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]