From: Simon Marchi <simon.marchi@polymtl.ca>
To: Sergio Durigan Junior <sergiodj@sergiodj.net>
Cc: Simon Marchi <simon.marchi@ericsson.com>, gdb-patches@sourceware.org
Subject: Re: [PATCH 2/4] x86-dregs: Print debug registers one per line
Date: Wed, 21 Jun 2017 21:06:00 -0000 [thread overview]
Message-ID: <9e9b1f0cd2508412684ac7817f2dd397@polymtl.ca> (raw)
In-Reply-To: <87injpccb9.fsf@sergiodj.net>
On 2017-06-21 22:31, Sergio Durigan Junior wrote:
> On Wednesday, June 21 2017, Simon Marchi wrote:
>
>> This get around this warning given by clang...
>>
>> /home/emaisin/src/binutils-gdb/gdb/nat/x86-dregs.c:209:7: error:
>> variable 'i' is incremented both in the loop header and in the loop
>> body [-Werror,-Wfor-loop-analysis]
>> i++;
>> ^
>> /home/emaisin/src/binutils-gdb/gdb/nat/x86-dregs.c:199:32: note:
>> incremented here
>> ALL_DEBUG_ADDRESS_REGISTERS (i)
>> ^
>>
>> ... I decided in the end to simply print the debug registers one per
>> line. I don't think it particularly helps readability to have them
>> two
>> per line anyway.
>
> Agreed, one per line sounds better to me.
>
>>
>> gdb/ChangeLog:
>>
>> * nat/x86-dregs.c (x86_show_dr): Print registers one per line.
>> ---
>> gdb/nat/x86-dregs.c | 16 ++++++----------
>> 1 file changed, 6 insertions(+), 10 deletions(-)
>>
>> diff --git a/gdb/nat/x86-dregs.c b/gdb/nat/x86-dregs.c
>> index 8c8adfa..58b1179 100644
>> --- a/gdb/nat/x86-dregs.c
>> +++ b/gdb/nat/x86-dregs.c
>> @@ -193,20 +193,16 @@ x86_show_dr (struct x86_debug_reg_state *state,
>> here. */
>> : "??unknown??"))));
>> debug_printf (":\n");
>> - debug_printf ("\tCONTROL (DR7): %s STATUS (DR6): %s\n",
>> - phex (state->dr_control_mirror, 8),
>> - phex (state->dr_status_mirror, 8));
>> +
>> + debug_printf ("\tCONTROL (DR7): 0x%s\n",phex
>> (state->dr_control_mirror, 8));
> ^^^
>
> Space after comma?
Yep, thanks.
>> + debug_printf ("\tSTATUS (DR6): 0x%s\n", phex
>> (state->dr_status_mirror, 8));
>> +
>> ALL_DEBUG_ADDRESS_REGISTERS (i)
>> {
>> - debug_printf ("\
>> -\tDR%d: addr=0x%s, ref.count=%d DR%d: addr=0x%s, ref.count=%d\n",
>> + debug_printf ("\tDR%d: addr=0x%s, ref.count=%d\n",
>> i, phex (state->dr_mirror[i],
>> x86_get_debug_register_length ()),
>> - state->dr_ref_count[i],
>> - i + 1, phex (state->dr_mirror[i + 1],
>> - x86_get_debug_register_length ()),
>> - state->dr_ref_count[i + 1]);
>> - i++;
>> + state->dr_ref_count[i]);
>> }
>> }
>>
>> --
>> 2.7.4
>
> LGTM. Thanks,
Thanks!
next prev parent reply other threads:[~2017-06-21 21:06 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-21 20:15 [PATCH 0/4] Get rid of some more warnings given by clang Simon Marchi
2017-06-21 20:15 ` [PATCH 3/4] dtrace-probe: Put semicolon after while on its own line Simon Marchi
2017-06-21 20:34 ` Sergio Durigan Junior
2017-06-21 21:08 ` Simon Marchi
2017-06-21 21:36 ` Pedro Alves
2017-06-25 10:48 ` Simon Marchi
2017-06-25 10:57 ` Simon Marchi
2017-06-21 20:15 ` [PATCH 1/4] environ-selftests: Ignore -Wself-move warning Simon Marchi
2017-06-21 20:29 ` Sergio Durigan Junior
2017-06-21 21:05 ` Simon Marchi
2017-06-21 21:12 ` Sergio Durigan Junior
2017-06-21 21:28 ` Pedro Alves
2017-06-21 21:32 ` Sergio Durigan Junior
2017-06-22 7:44 ` Simon Marchi
2017-06-22 9:34 ` Pedro Alves
2017-06-21 21:16 ` Simon Marchi
2017-06-21 21:30 ` Sergio Durigan Junior
2017-06-22 8:31 ` [PATCH v2] " Simon Marchi
2017-06-22 9:51 ` Pedro Alves
2017-06-22 10:52 ` Pedro Alves
2017-06-22 10:57 ` Simon Marchi
2017-06-22 11:43 ` Pedro Alves
2017-06-21 20:15 ` [PATCH 2/4] x86-dregs: Print debug registers one per line Simon Marchi
2017-06-21 20:31 ` Sergio Durigan Junior
2017-06-21 21:06 ` Simon Marchi [this message]
2017-06-25 10:58 ` Simon Marchi
2017-06-21 20:15 ` [PATCH 4/4] main: Don't add int to string Simon Marchi
2017-06-21 20:35 ` Sergio Durigan Junior
2017-06-25 10:58 ` Simon Marchi
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=9e9b1f0cd2508412684ac7817f2dd397@polymtl.ca \
--to=simon.marchi@polymtl.ca \
--cc=gdb-patches@sourceware.org \
--cc=sergiodj@sergiodj.net \
--cc=simon.marchi@ericsson.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