This is the mail archive of the
gdb-patches@sourceware.org
mailing list for the GDB project.
Re: [PATCH] -stack-info-depth should always return a count.
- From: Eli Zaretskii <eliz at gnu dot org>
- To: Andrew Burgess <aburgess at broadcom dot com>
- Cc: gdb-patches at sourceware dot org
- Date: Thu, 27 Mar 2014 19:09:21 +0200
- Subject: Re: [PATCH] -stack-info-depth should always return a count.
- Authentication-results: sourceware.org; auth=none
- References: <53342599 dot 9000206 at broadcom dot com>
- Reply-to: Eli Zaretskii <eliz at gnu dot org>
> Date: Thu, 27 Mar 2014 13:20:25 +0000
> From: Andrew Burgess <aburgess@broadcom.com>
>
> +* MI changes
> +
> + ** The -stack-info-depth command will now always return a depth even if
> + stack corruption is encountered. A new reason string is also returned
> + that explains why gdb is reporting this depth.
^^^
"GDB", in caps.
> +Return the depth of the stack. If the integer argument
> +@var{max-depth} is specified, do not count beyond @var{max-depth}
> +frames. The reason why gdb returns the answer it does is also given.
^^^
@value{GDBN}
> +Possible reasons are @var{All frames}, @var{Reached frame limit}, or
> +an error message.
@var is incorrect here, please use @samp instead.
> +An example where there are 3 valid stack frames, after which the stack
> +pointer is corrupted and gdb is unable to unwind the stack further:
^^^
@value{GDBN}
The documentation parts are OK with those changes.
Thanks.