From: Pedro Alves <palves@redhat.com>
To: Yao Qi <yao@codesourcery.com>
Cc: Pedro Alves <palves@redhat.com>, gdb-patches@sourceware.org
Subject: Re: [PATCH] Only print entry values for arguments.
Date: Thu, 08 Aug 2013 14:24:00 -0000 [thread overview]
Message-ID: <5203A9F7.5060907@redhat.com> (raw)
In-Reply-To: <52033CB7.3070202@codesourcery.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
next prev parent reply other threads:[~2013-08-08 14:24 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-05 0:45 Yao Qi
2013-08-05 2:10 ` Yao Qi
2013-08-05 14:12 ` Pedro Alves
2013-08-08 6:38 ` Yao Qi
2013-08-08 14:24 ` Pedro Alves [this message]
2013-08-14 9:46 ` Yao Qi
2013-08-14 11:17 ` Pedro Alves
2013-08-14 11:54 ` Yao Qi
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=5203A9F7.5060907@redhat.com \
--to=palves@redhat.com \
--cc=gdb-patches@sourceware.org \
--cc=yao@codesourcery.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox