This is the mail archive of the
gdb-patches@sourceware.org
mailing list for the GDB project.
Re: [PATCH 5/5] set/show code-cache NEWS and doc
- From: Eli Zaretskii <eliz at gnu dot org>
- To: Yao Qi <yao at codesourcery dot com>
- Cc: gdb-patches at sourceware dot org
- Date: Thu, 24 Oct 2013 18:20:44 +0300
- Subject: Re: [PATCH 5/5] set/show code-cache NEWS and doc
- Authentication-results: sourceware.org; auth=none
- References: <1382516855-32218-1-git-send-email-yao at codesourcery dot com> <1382516855-32218-6-git-send-email-yao at codesourcery dot com> <83sivshuux dot fsf at gnu dot org> <5268D967 dot 2000703 at codesourcery dot com>
- Reply-to: Eli Zaretskii <eliz at gnu dot org>
> Date: Thu, 24 Oct 2013 16:25:11 +0800
> From: Yao Qi <yao@codesourcery.com>
> CC: <gdb-patches@sourceware.org>
>
> On 10/23/2013 11:25 PM, Eli Zaretskii wrote:
> > Thanks. However, this (and even more importantly, the manual) should
> > explain what is "code" in this context. "Code" is too general a word
> > to hope that the reader will immediately understand what you mean.
> >
>
> I go through gdb.texinfo, and find "program code" is used in some
> places. I choose it.
The problem in this case is that it's unclear whether you are talking
about accessing the source code or the code (a.k.a. ".text") section
of the executable. "Program code" could mean either of these two.
> > Also, the last sentence above should be in the manual; it's not good
> > that the manual has less details than NEWS.
>
> OK, add one line in the manual to mention that this improves
> disassemble. How about this?
Replace "disassemble" with "disassembly", and I'm happy.
Thanks.