stdpaths

stdpaths

Examples: "stdpaths"

Print out all paths set for standard directories

See Also: pwd, dirs.

step

step

Examples:

"step": execute the next instruction
"s"

Execute the patient by a single machine instruction.

If waitForPatient is non-zero, step waits for the machine to stop again.
This doesn't do any of the checks for special conditions (XchgTopStack, software interrupts, etc.) performed by the `s' command in istep.

See Also: istep, next.

step-patient

step-patient

Examples:

"step-patient": Execute a single instruction on the target PC.

Causes the PC to execute a single instruction, returning only when the instruction has been executed.

Unlike the continue-patient command, this command will not return until the machine has stopped again.
No other thread will be allowed to run, as timer interrupts will be turned off while the instruction is being executed.

See Also: help-fetch.

step-until

step-until expression [byte|word]

Examples:

"step-until ax=0": Single-step until ax is zero.
"step-until ds:20h!=0 byte": Single-step until byte at ds:20h is non-zero
"step-until ds:20h!=0 word": Single-step until word at ds:20h is non-zero
"step-until c=0": Single-step until the carry is clear
"step-until ax!=ax": Step forever

This command causes Swat to step until a condition is met.

Useful for tracking memory or register trashing bugs.

stop

stop in <class>::<message> [if <expr>]
stop in <procedure> [if <expr>]
stop in <address-history-token> [if <expr>]
stop at [<file>:]<line> [if <expr>]
stop <address> [if <expr>]

Examples: "stop in main"
"stop in @3"
"stop at /staff/pcgeos/Loader/main.asm:36 if { joe_local ==22}"
"stop at 25"
"stop MemAlloc+3 if {ax==3}"

Specify a place and condition at which the machine should stop executing. This command is intended primarily for setting breakpoints when debugging a geode created in C or another high-level language, but may also be used when debugging assembly-language geodes.

"stop in" will set a breakpoint at the beginning of a procedure, immediately after the procedure's stack frame has been set up.
"stop at" will set a breakpoint at the first instruction of the given source line. If no <file> is specified, the source file for the current stack frame is used.
If a condition is specified, by means of an "if <expr>" clause, you should enclose the expression in {}'s to prevent any nested commands, such as a "value fetch" command, from being evaluated until the break-point is hit.
For convenience, "stop in" also allows address-history tokens. This is useful when used in conjunction with the "methods" command.

See Also: brk, ibrk.

stop-catch

stop-catch <body>

Examples:

"stop-catch {go ProcCallModuleRoutine}": Let machine run until it reaches ProcCallModuleRoutine() , but do not issue a FULLSTOP event when it gets there.

Allows a string of commands to execute without a FULLSTOP event being generated while they execute.

A number of things happen when a FULLSTOP event is dispatched, including notifying the user where the machine stopped. This is inappropriate in something like "istep" or "cycles" that is single-stepping the machine, for example.

See Also: event, continue-patient, step-patient.

stop-patient

stop-patient

Examples:

"stop-patient": Stops the target PC.

Stops the target PC, in case you continued it and didn't wait for it to stop on its own.

This is different from the "stop" subcommand of the "patient" command.

See Also: continue-patient.

GEOS SDK TechDocs |

smatch ... | Next:

stream ...