Set a breakpoint on every function entry point or on every instruction.
stop [quiet] every procedure entry [thread ID {,...}][if cond] [commands] stop [quiet] every instruction [thread ID {,...}][if cond] [commands]
ID |
A thread ID. |
cond |
A conditional expression. |
commands |
A list of debugger commands. |
This command sets a breakpoint on every entry point to a function in the program, or on every instruction in the program.
To suppress status reporting messages when the debugger hits a breakpoint, specify quiet.
To set a breakpoint such that the debugger stops when it hits one or more specific threads, specify thread and one or more comma-separated thread IDs.
To set a breakpoint based on a conditional expression, specify if cond.
To run one or more commands upon hitting a breakpoint, specify commands.
A disadvantage of this command is that it establishes breakpoints for hundreds or even thousands of entry points about which you have little or no information. For example, if you use stop every procedure entry immediately after loading a program and then run it, the debugger will stop or trace over 100 entry points before reaching your main entry point. About the only thing that you can do if execution stops at most such unknown places is continue until some function relevant to your debugging is reached.
This command can be very time consuming because the debugger searches your entire program, including all shared libraries that it references, and establishes breakpoints for every entry point in every executable image. This can also considerably slow execution of your program as it runs.
Copyright © 1996-2010, Intel Corporation. All rights reserved.