From aaa11abe428e6433b3e41fb88431886f4445a462 Mon Sep 17 00:00:00 2001 From: Andrew Cagney Date: Sat, 22 Nov 1997 12:52:44 +0000 Subject: Clarify meaning of sim_signalled's SIGRC argument. Document that this isn't possible in sim-reason.c and just return the target SIGRC instead. For simulators that rely on sim-reason.c, replace SIG* with SIM_SIG*. Hack nrun.c so that when it is executed (ARGV[0]) as `step' instead of `run' it single steps the simulator. Allows testing of single step without full GDB. --- include/remote-sim.h | 7 +++++-- 1 file changed, 5 insertions(+), 2 deletions(-) (limited to 'include/remote-sim.h') diff --git a/include/remote-sim.h b/include/remote-sim.h index c4fecc0..a785437 100644 --- a/include/remote-sim.h +++ b/include/remote-sim.h @@ -223,8 +223,11 @@ int sim_stop PARAMS ((SIM_DESC sd)); undefined memory region (SIGSEGV); Mis-aligned memory access (SIGBUS). - SIM_SIGNALLED: The simulator encountered target code that requires - the signal SIGRC to be delivered to the simulated program. + SIM_SIGNALLED: The program has stopped. The simulator has + encountered target code that requires the (HOST) signal SIGRC to be + delivered to the simulated program. Ex: `kill (getpid (), + TARGET_SIGxxx)'. Where TARGET_SIGxxx has been translated into a + host signal. FIXME: This is not always possible.. SIM_RUNNING, SIM_POLLING: The return of one of these values indicates a problem internal to the simulator. */ -- cgit v1.1