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.


Andreas Schwab wrote:
Andrew Cagney <ac131313@redhat.com> writes:


Andreas Schwab wrote:

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.

The sig* tests check this edge case.


Not this one.  There are only two failures, which are
"gdb.base/sigstep.exp: finish from handleri; leave handler (timeout)" and
"gdb.base/sigstep.exp: finish from handleri; leave signal trampoline", and
neither are not due to internal errors.

The "step on breakpoint; ..." tests, based on your description, exercise just that senario. They run to a breakpoint, wait for a signal to be come pending, and then try to step et.al.


Sounds like more is going on?

Andrew

Ref 1757, 1738


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