This is the mail archive of the
gdb-patches@sourceware.org
mailing list for the GDB project.
Re: [PATCH] Only print entry values for arguments.
- From: Pedro Alves <palves at redhat dot com>
- To: Yao Qi <yao at codesourcery dot com>
- Cc: Pedro Alves <palves at redhat dot com>, gdb-patches at sourceware dot org
- Date: Thu, 08 Aug 2013 15:23:51 +0100
- Subject: Re: [PATCH] Only print entry values for arguments.
- References: <1375663450-5825-1-git-send-email-yao at codesourcery dot com> <51FFB2A5 dot 8040005 at redhat dot com> <52033CB7 dot 3070202 at codesourcery dot com>
>> Otherwise it looks good to me. I wonder whether we should put
>> this in 7.6.1 ?
>
> This problem exists on 7.6 branch too,
>
> (gdb) interpreter-exec mi "-stack-list-locals 2"
> ^done,locals=[{name="b",type="int",value="2"}]
> (gdb) set print entry-values only
> (gdb) interpreter-exec mi "-stack-list-locals 2"
> ^done,locals=[{name="b@entry",type="int",value="<optimized out>"}]
>
> We can apply this patch to 7.6 branch except the test case part,
> because gdb.trace/mi-trace-unavailable.exp doesn't exist on 7.6
> branch.
If we run 7.6 against that test pristine would it pass cleanly?
> I plan to
> 1) cvs -d :ext:qiyao@sourceware.org:/cvs/src co -r gdb_7_6-branch gdb
> 2) apply this patch without changes to gdb.trace/mi-trace-unavailable.exp
>
> Since it is not a bug fix, don't have to mention it in
> http://sourceware.org/gdb/wiki/GDB_7.6_Release .
Hmm. If this is issue is present in the 7.6 branch, how is it
not a bug fix? Instead, what we should do if the bug wasn't
reported in bugzilla, is file one, so we can reference it from
the wiki.
> If my understanding
> is right, I'll commit the patch to 7.6 branch.
--
Pedro Alves