Hello,

The attached fixes a bug with step/next across signals.  Given:

	Breakpoint at 10 hit
	10	while (!done);
	(gdb) next

when there was a signal pending (that set DONE), GDB would:

Attempt to step of the breakpoint at "10":
- pull all breakpoints
- PT_STEP (to get off the BP instruction)
- get back the signal instead

Attempt to skip the signal handler:
- add a step_resume_breakpoint at "10" the signal return addr
- PT_STEP delivering the signal
- insert all breakpoints (including step_resume)
- PT_CONTINUE the inferior
- get back SIGTRAP from the step_resume breakpoint
- delete the step_resume bp

Go back to doing the next:
- PT_STEP the inferior (breakpoints including "10" still inserted)
- re-hit "10"

the problem is that GDB forgot that it was, at the time of the signal, 
trying to step off a breakpoint.

The attached patch fixes this, it notes if/when it was stepping off a 
breakpoint, so that it can return to that task once the 
step-resume-breakpoint is hit.

I've tested it on a my patched PPC/NetBSD kernel and it KPASSes 1757; 
and a vanila rhel3u2 system with no test changes.

Since the 1757 KFAILs pass, I've removed them as `obvious'.

comments?
Andrew