Tornado

5
Shell
tWdbTask 0x3f024 398e04 3 READY 405ac 398d50 30067 0
tNetTask _netTask 3b39e0 50 PEND 405ac 3b3988 0 0
value = 0 = 0x0
If you want to debug an application you have loaded dynamically, set an
appropriate breakpoint and spawn a task which runs when you continue the
system:
-> sysSuspend
value = 0 = 0x0
-> ld < test.o
Loading /view/didier.temp/vobs/wpwr/target/lib/objMC68040gnutest//test.o /
value = 400496 = 0x61c70 = _rn_addroute + 0x1d4
-> b address
value = 0 = 0x0
-> sp test
value = 0 = 0x0
-> c
5
The application breaks on address when the instruction at address is executed.
5.2.7 Interrupting a Shell Command
Occasionally it is desirable to abort the shell’s evaluation of a statement. For
example, an invoked routine may loop excessively, suspend, or wait on a
semaphore. This may happen as the result of errors in arguments specified in the
invocation, errors in the implementation of the routine itself, or simply oversight
as to the consequences of calling the routine.
To regain control of the shell in such cases, press the interrupt character on the
keyboard, usually CTRL+C. 2 This makes the shell stop waiting for a result and
allows input of a new statement. Any remaining portions of the statement are
discarded and the task that ran the function call is deleted.
Pressing CTRL+C is also necessary to regain control of the shell after calling a
routine on the target that ends with exit( ) rather than return.
Occasionally a subroutine invoked from the shell may incur a fatal error, such as a
bus/address error or a privilege violation. When this happens, the failing routine
is suspended. If the fatal error involved a hardware exception, the shell
automatically notifies you of the exception. For example:
2. The interrupt character matches whatever you normally use in UNIX shells as an interrupt;
you can set it with the UNIX command stty intr. See your host system documentation for
details.
173