Command Directory

ignore

Note: It is better to drop a request than to ignore it because run-time overhead may be associated with ignored requests, but not with dropped ones. [cautionend]

Format 1: Format 1 lets you ignore breakpoint or action requests at specified hooks. See Using Debugger Commands for details on the HOOK-TYPE argument, an argument that allows you to specify hooks.

Format 2: Format 2 causes the debugger to ignore all signals.

Format 3: Format 3 causes the specific signal named in SIGNAL-NAME to be ignored when SIGNAL-NAME is used with the signal keyword. SIGNAL-NAME is the name of a signal. Tracing of the signal is turned off. See Chapter 17, "Signal-Handling Functions," in the SAS/C Library Reference, Volume 1, for a list of signal names.

Dropping ignore: You can drop the ignore command (using the drop command) if you want the breakpoint requests and actions to be in effect again or if you do not want to ignore signals.

Identical requests: If an ignore request is made that is identical to an existing one, the identical request is not installed. This is true whether the request to be installed is within an on command or typed in at the command line.

ignore *: ignores all breakpoint and action requests at every line-hook for every source file.
ignore entry: ignores requests at all function entries.
ignore main 45: ignores any requests at line 45 in the main function.
ignore 53: ignores any requests at line 53 of the current function.
ignore (comp23) entry: ignores any requests made at entry to the comp23 compilation.
ignore func1 entry: ignores any requests made at entry to the func1 function.
ignore func 23:46: ignores any requests at lines 23 through 46 in the func function.
ignore signal: ignores all signals.
ignore SIGSEGV signal: ignores the signal named SIGSEGV.

	Successful: request number from `query`
	Unsuccessful : 0