diff options
author | Andrew Burgess <aburgess@redhat.com> | 2023-01-18 12:54:49 +0000 |
---|---|---|
committer | Andrew Burgess <aburgess@redhat.com> | 2023-01-25 15:48:57 +0000 |
commit | 5da8359356ae4f9db3a46c3b167941481aae05ab (patch) | |
tree | fa2fb2dd6f61dc7efe2a093e4b073d541c522b37 | |
parent | 413577a313ff22facbf72413dede0b1603bc58a5 (diff) | |
download | binutils-gdb-5da8359356ae4f9db3a46c3b167941481aae05ab.tar.gz |
gdb/doc: extend the documentation for conditional breakpoints
This documentation update adds more text to describe what happens if a
conditional breakpoint calls an inferior function, and the inferior
function is interrupted for some reason.
-rw-r--r-- | gdb/doc/gdb.texinfo | 11 |
1 files changed, 11 insertions, 0 deletions
diff --git a/gdb/doc/gdb.texinfo b/gdb/doc/gdb.texinfo index f1b99152abb..1c92b644908 100644 --- a/gdb/doc/gdb.texinfo +++ b/gdb/doc/gdb.texinfo @@ -5713,6 +5713,17 @@ conditions for the purpose of performing side effects when a breakpoint is reached (@pxref{Break Commands, ,Breakpoint Command Lists}). +If a breakpoint condition calls a function in your program, then it is +possible that your program could stop for some reason while in the +called function. For example, @value{GDBN} might hit a breakpoint in +the called function, or the called function may receive a signal +(e.g.@ a @code{SIGSEGV}) as a result of some undefined behaviour, if +this happens then @value{GDBN} will stop. Depending on the settings +@code{unwindonsignal} and @code{unwind-on-terminating-exception} +(@pxref{Calling,,Calling Program Functions}) @value{GDBN} may unwind +the stack back to the breakpoint location, or may leave the program at +the frame where the stop occurred. + Breakpoint conditions can also be evaluated on the target's side if the target supports it. Instead of evaluating the conditions locally, @value{GDBN} encodes the expression into an agent expression |