From: Pedro Alves <palves@redhat.com>
To: Simon Marchi <simark@simark.ca>,
Philippe Waroquiers <philippe.waroquiers@skynet.be>,
gdb-patches@sourceware.org
Subject: Re: [RFA] Implement 'print -raw-values' and 'set print raw-values on|off'
Date: Wed, 04 Dec 2019 17:19:00 -0000 [thread overview]
Message-ID: <7e1cdc30-b8c0-2fb0-0fe6-2284b8c7db93@redhat.com> (raw)
In-Reply-To: <189517a9-1d4f-fc2c-f159-3356b745240b@simark.ca>
On 12/4/19 4:34 PM, Simon Marchi wrote:
> On 2019-12-04 11:24 a.m., Pedro Alves wrote:
>> On 12/4/19 3:43 AM, Simon Marchi wrote:
>>> I'm just a bit worried about the naming, but I don't have anything better
>>> to suggest. I mention it in case you do. The "set print raw-values" sounds
>>> like superset of "set print raw-frame-arguments", because in my mind frame
>>> arguments are printed as values.
>>
>> But isn't it a superset?
>
> From my testing, "set print raw-values on/off" didn't affect how parameter values
> were printed in "bt" or "frame". But I might have tested it wrong.
Hmm, print_frame_arg does:
vp_opts.raw = fp_opts.print_raw_frame_arguments;
and I guess that is what ends up ignoring whatever's
the "set print raw-values" setting, even if you don't
explicitly specify "-raw-frame-arguments".
Thanks,
Pedro Alves
next prev parent reply other threads:[~2019-12-04 17:19 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-07 19:39 Philippe Waroquiers
2019-08-07 21:38 ` Tom Tromey
2019-08-08 18:59 ` Philippe Waroquiers
2019-08-08 17:25 ` Eli Zaretskii
2019-09-07 11:42 ` PING " Philippe Waroquiers
2019-09-29 15:29 ` PING^2 " Philippe Waroquiers
2019-09-29 15:33 ` Eli Zaretskii
2019-09-29 15:49 ` Philippe Waroquiers
2019-10-20 10:26 ` PING^3 " Philippe Waroquiers
2019-12-04 16:18 ` Pedro Alves
2019-12-04 3:43 ` Simon Marchi
2019-12-04 16:24 ` Pedro Alves
2019-12-04 16:34 ` Simon Marchi
2019-12-04 17:19 ` Pedro Alves [this message]
2019-12-07 14:01 ` Philippe Waroquiers
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=7e1cdc30-b8c0-2fb0-0fe6-2284b8c7db93@redhat.com \
--to=palves@redhat.com \
--cc=gdb-patches@sourceware.org \
--cc=philippe.waroquiers@skynet.be \
--cc=simark@simark.ca \
/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