This is the mail archive of the
gdb-patches@sourceware.org
mailing list for the GDB project.
Re: [PATCH 5/7] DOC and NEWS
- From: Eli Zaretskii <eliz at gnu dot org>
- To: Yao Qi <yao at codesourcery dot com>
- Cc: gdb-patches at sourceware dot org
- Date: Fri, 20 Sep 2013 11:21:16 +0300
- Subject: Re: [PATCH 5/7] DOC and NEWS
- Authentication-results: sourceware.org; auth=none
- References: <1378641807-24256-1-git-send-email-yao at codesourcery dot com> <1379645226-8719-1-git-send-email-yao at codesourcery dot com> <1379645226-8719-6-git-send-email-yao at codesourcery dot com>
- Reply-to: Eli Zaretskii <eliz at gnu dot org>
> From: Yao Qi <yao@codesourcery.com>
> Date: Fri, 20 Sep 2013 10:47:04 +0800
>
>
> -V3: Mention "in remote debugging".
>
> gdb:
>
> 2013-09-20 Yao Qi <yao@codesourcery.com>
>
> * NEWS: Describe the default option of
> "trust-readonly-sections" becomes "auto" and the related
> changes.
>
> gdb/doc:
>
> 2013-09-20 Yao Qi <yao@codesourcery.com>
>
> * gdb.texinfo (File): Mention that user has
> 'set trust-readonly-sections off' to get updated contents if
> they are modified. Explain the default option of
> "trust-readonly-sections" is "auto".
This is OK, but should we perhaps mention that an attempt to write to
a read-only section will cause the prompt to turn this option off? I
would mention that prompt as part of this text:
> @item set trust-readonly-sections off
> Tell @value{GDBN} not to trust readonly sections. This means that
> the contents of the section might change while the program is running,
> -and must therefore be fetched from the target when needed.
> +and must therefore be fetched from the target when needed. If you
> +modified the code in the target program, you have to
> +@code{set trust-readonly-sections off} to guarantee @value{GDBN} reads
> +updated contents from the target program instead of object file.
Thanks.