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 <cagney@gnu.org> writes:


The "step on breakpoint; ..." tests,


I can't find any such test in gdb.base.

sigstep.exp:breakpoint_over_handler, added 25/8. The above should be in your gdb.log. What's your GDB version?


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?


Perhaps the key point is that the signal (SIGIO) is silently passed to the
inferiour by gdb.

No, the above does that (but with SIGALRM). Are there multiple signals pending?


Andrew


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