Re: internal-error: insert_step_resume_breakpoint_at_sal

Nick Roberts
2005-02-06T07:26:27Z

> First thing I'd do is run the sig*.exp tests to see which are failing -
> if the kernel's working correctly they all pass.

Running ./gdb.base/sigall.exp ...
Running ./gdb.base/sigaltstack.exp ...
Running ./gdb.base/sigbpt.exp ...
KFAIL: gdb.base/sigbpt.exp: stepi; stepi out of handler (executed fault insn) (PRMS: gdb/1702)
KFAIL: gdb.base/sigbpt.exp: stepi bp before segv; stepi out of handler (executed fault insn) (PRMS: gdb/1702)
KFAIL: gdb.base/sigbpt.exp: stepi bp at segv; stepi out of handler (corrupt pc) (PRMS: gdb/1702)
KFAIL: gdb.base/sigbpt.exp: stepi bp before and at segv; stepi out of handler (corrupt pc) (PRMS: gdb/1702)
Running ./gdb.base/siginfo.exp ...
Running ./gdb.base/signals.exp ...
KFAIL: gdb.base/signals.exp: override SIGINT (PRMS: gdb/1707)
Running ./gdb.base/signull.exp ...
Running ./gdb.base/sigrepeat.exp ...
Running ./gdb.base/sigstep.exp ...
KFAIL: gdb.base/sigstep.exp: step on breakpoint, to handler; performing step (PRMS: gdb/1738)
KFAIL: gdb.base/sigstep.exp: next on breakpoint, to handler; performing next (PRMS: gdb/1738)
KFAIL: gdb.base/sigstep.exp: continue on breakpoint, to handler; performing continue (PRMS: gdb/1738)
KFAIL: gdb.base/sigstep.exp: step on breakpoint, to handler entry; performing step (PRMS: gdb/1738)
KFAIL: gdb.base/sigstep.exp: next on breakpoint, to handler entry; performing next (PRMS: gdb/1738)
KFAIL: gdb.base/sigstep.exp: continue on breakpoint, to handler entry; performing continue (PRMS: gdb/1738)

Note though, that many other tests fail too. What's the simplest way to run an
individual test? I used:

/home/nick/src/gdb/../dejagnu/runtest -tool gdb GDB=../gdb ./gdb.base/sigbpt.exp

but that can't be right.

Nick