Re: internal-error: insert_step_resume_breakpoint_at_sal

Andrew Cagney
2005-01-20T17:07:09Z

Nick Roberts wrote:
> > > Well symtab = 0x0 looks unassigned to me.
> >
> > More likely not-found, what's at that address?
>
> Whats at 0x0?! Are you winding me up, or is it some kind of offset?

What's at $pc (where PC is 0x4012e7e9 or 0x80850d5), symtab==0 indicates
a symtab lookup failure.

> > Can you capture the output from "set debug infrun 1"? It should help.
>
> See below. I can send the full transcript if necessary.

How much more?

> Nick
>
> ...
> infrun: TARGET_WAITKIND_STOPPED
> infrun: stop_pc = 0x4012e7e9
> infrun: random signal 20
> infrun: resume (step=0, signal=20)
> infrun: prepare_to_wait
> infrun: infwait_normal_state
> infrun: TARGET_WAITKIND_STOPPED
> infrun: stop_pc = 0x4012e7e9
> infrun: random signal 20
> infrun: resume (step=0, signal=20)
>
> infrun: prepare_to_wait
> Breakpoint 3, Fsplit_window (window=137726961, size=137726961,
> horflag=137726961) at window.c:3688
> 3688 if (NILP (window))
> (gdb) n

There appears to be stuff missing here, the output should contain
something like:

resume(step=1, signal=0)
resume(step=0, signal=0)

as GDB single-steps the thread off breakpoint 3. The PC should be near
or at 0x80850d5 found in the below.

> infrun: infwait_normal_state
> infrun: TARGET_WAITKIND_STOPPED
> infrun: stop_pc = 0x4012e7e9
> infrun: random signal 20
> infrun: resume (step=0, signal=20)
> infrun: prepare_to_wait
> infrun: infwait_normal_state
> infrun: TARGET_WAITKIND_STOPPED
> infrun: stop_pc = 0x4012e7e9
> infrun: random signal 20
> infrun: resume (step=0, signal=20)
> infrun: prepare_to_wait
> infrun: infwait_normal_state
> infrun: TARGET_WAITKIND_STOPPED
> infrun: stop_pc = 0x80850d5
> infrun: BPSTATE_WHAT_STOP_NOISY
> infrun: stop_stepping
>
> Breakpoint 1, internal_error (file=0x82214d7 "infrun.c", line=2671,
> string=0x81ef681 "%s: Assertion `%s' failed.") at utils.c:789
> 789 va_start (ap, string);
>

Andrew