[PATCHv2 01/13] gdb/doc: extended documentation for inferior function calls
Eli Zaretskii
eliz@gnu.org
Wed Jan 18 17:20:15 GMT 2023
> Cc: Andrew Burgess <aburgess@redhat.com>
> Date: Wed, 18 Jan 2023 16:17:57 +0000
> From: Andrew Burgess via Gdb-patches <gdb-patches@sourceware.org>
>
> I noticed that the documentation for inferior function calls doesn't
> say much about what happens if/when an inferior function call is
> interrupted, i.e. it doesn't describe what the dummy frame looks like
> on the stack, or how GDB behaves when the inferior is continued and
> reaches the dummy frame.
>
> This commit aims to add some of this missing information.
Thanks.
> +If a called function is interrupted for any reason, and the stack is
> +not unwound (due to @code{set unwind-on-terminating-exception on} or
> +@code{set unwindonsignal on}),
Please add here a cross-reference to here these settings are described
in the manual.
Otherwise, this is OK.
More information about the Gdb-patches
mailing list