From: Tom Tromey <tom@tromey.com>
To: Pedro Alves <palves@redhat.com>
Cc: Tom Tromey <tom@tromey.com>, gdb-patches@sourceware.org
Subject: Re: [RFA 1/2] Fix two regressions in scalar printing
Date: Mon, 14 Aug 2017 15:22:00 -0000 [thread overview]
Message-ID: <87h8xauqd9.fsf@pokyo> (raw)
In-Reply-To: <707a03e4-46ef-cea9-f098-cc687b02d31e@redhat.com> (Pedro Alves's message of "Mon, 14 Aug 2017 15:02:47 +0100")
>>>>> "Pedro" == Pedro Alves <palves@redhat.com> writes:
Pedro> Sorry for dropping the ball on this. I wanted to be sure that
Pedro> we have tests for the
Pedro> (gdb) p /u -1
Pedro> $1 = 4294967295
Pedro> (gdb) p /d (unsigned long long) -1
Pedro> $2 = -1
Pedro> etc. issues discussed earlier. Do you know whether there's some tests for
Pedro> that already somewhere, but might have simply been missed before for
Pedro> running both patches together?
Good question. I think what happened is that this change had some
fallout elsewhere, which is why there are also some test changes in the
patch.
However, these are kind of indirect, so I added tests for
"print/d (unsigned char) -1" and "print/u (char) -1".
>> +# Regression test for PR gdb/21675
>> +proc test_radices {} {
>> + gdb_test "print/o 16777211" " = 077777773"
>> + gdb_test "print/d 1.5" " = 1\[^.\]"
>> + gdb_test "print/u 1.5" " = 1\[^.\]"
Pedro> What's the reason for the "\[^.\]" part of the regexes?
Pedro> What's that trying to match? Why not simply " = 1" ?
I was worried that this would erroneously match "1.5" or the like; but I
tried it and I see my fears are unfounded. So, I changed these to " = 1".
Tom
next prev parent reply other threads:[~2017-08-14 15:22 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20170713123400.28917-1-tom@tromey.com>
2017-07-13 12:34 ` [RFA 2/2] Remove BITS_IN_BYTES define Tom Tromey
2017-07-14 15:16 ` Pedro Alves
2017-07-14 16:15 ` Tom Tromey
2017-07-13 12:35 ` [RFA 1/2] Fix two regressions in scalar printing Tom Tromey
2017-07-14 14:56 ` Pedro Alves
2017-07-14 15:20 ` Eli Zaretskii
2017-07-14 16:50 ` Tom Tromey
2017-07-14 17:25 ` Pedro Alves
2017-07-31 22:03 ` Tom Tromey
2017-08-14 14:02 ` Pedro Alves
2017-08-14 15:22 ` Tom Tromey [this message]
2017-08-14 15:43 ` Tom Tromey
2017-08-14 15:52 ` Pedro Alves
2017-08-17 2:24 ` Tom Tromey
2017-12-10 14:15 ` Regression on 32-bit: gdb.guile/scm-ports.exp [Re: [RFA 1/2] Fix two regressions in scalar printing] Jan Kratochvil
2017-07-14 15:19 ` [RFA 1/2] Fix two regressions in scalar printing Jonah Graham
2017-08-25 16:54 ` Thomas Preudhomme
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=87h8xauqd9.fsf@pokyo \
--to=tom@tromey.com \
--cc=gdb-patches@sourceware.org \
--cc=palves@redhat.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