From: "Andrew Burgess" <aburgess@broadcom.com>
To: "Jan Kratochvil" <jan.kratochvil@redhat.com>,
"Pedro Alves" <palves@redhat.com>
Cc: gdb-patches@sourceware.org
Subject: Re: Regression for implptr.exp and pieces.exp [Re: [COMMIT PATCH] value_bits_valid: Fix latent bug.]
Date: Tue, 09 Jul 2013 14:16:00 -0000 [thread overview]
Message-ID: <51DC1B1A.5090203@broadcom.com> (raw)
In-Reply-To: <20130709095442.GA20006@host2.jankratochvil.net>
On 09/07/2013 10:54 AM, Jan Kratochvil wrote:
> On Mon, 08 Jul 2013 12:22:17 +0200, Andrew Burgess wrote:
>> On 05/07/2013 7:21 PM, Pedro Alves wrote:
>>> On 07/05/2013 04:20 PM, Andrew Burgess wrote:
>>>
>>>> 2013-07-05 Andrew Burgess <aburgess@broadcom.com>
>>>>
>>>> * value.c (value_bits_valid): If the value is not lval_computed
>>>> or has no check validity handler then the answer is the
>>>> optimized_out flag, otherwise defer to the handler.
>>>
>>> OK.
>>
>> Committed.
>
> On any platform I test for 32-bit targets (either on i386 native host or on
> x86_64 host with -m32 target cflags) I get:
>
> 9f5e30f7cf73a3256fbb9a265c897aa3f2c91439 is the first bad commit
> commit 9f5e30f7cf73a3256fbb9a265c897aa3f2c91439
> Author: aburgess <aburgess>
> Date: Mon Jul 8 10:21:33 2013 +0000
>
> Fix bug in value_bits_valid.
>
> http://sourceware.org/ml/gdb-patches/2013-07/msg00174.html
>
> * value.c (value_bits_valid): If the value is not lval_computed
> or has no check validity handler then the answer is the
> optimized_out flag, otherwise defer to the handler.
>
> Running gdb/testsuite/gdb.dwarf2/implptr.exp ...
> -PASS: gdb.dwarf2/implptr.exp: print j in implptr:bar
> +FAIL: gdb.dwarf2/implptr.exp: print j in implptr:bar
> -PASS: gdb.dwarf2/implptr.exp: print p[0].x in implptr:foo
> +FAIL: gdb.dwarf2/implptr.exp: print p[0].x in implptr:foo
>
> Running gdb/testsuite/gdb.dwarf2/pieces.exp ...
> -PASS: gdb.dwarf2/pieces.exp: print a.i in pieces:f3
> -PASS: gdb.dwarf2/pieces.exp: print a.j in pieces:f3
> -PASS: gdb.dwarf2/pieces.exp: set a.i in pieces:f3
> -PASS: gdb.dwarf2/pieces.exp: print new a.i in pieces:f3
> +FAIL: gdb.dwarf2/pieces.exp: print a.i in pieces:f3
> +FAIL: gdb.dwarf2/pieces.exp: print a.j in pieces:f3
> +FAIL: gdb.dwarf2/pieces.exp: set a.i in pieces:f3
> +FAIL: gdb.dwarf2/pieces.exp: print new a.i in pieces:f3
>
I've committed a patch to revert all the changes done by Pedro and
myself to value_bits_valid, this is what Pedro was going to do anyway here:
http://sourceware.org/ml/gdb-patches/2013-07/msg00200.html
before I jumped in.
Looking again at this function I don't believe either the original (now
current again) version, or any of the versions we've tried are actually
correct, but fixing this properly is going to be slightly more involved,
and I don't have time to put the patch together today.
Sorry for the inconvenience.
Andrew.
next prev parent reply other threads:[~2013-07-09 14:16 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-04 16:09 [COMMIT PATCH] value_bits_valid: Fix latent bug Pedro Alves
2013-07-05 14:42 ` Andrew Burgess
2013-07-05 15:06 ` Pedro Alves
2013-07-05 15:20 ` Andrew Burgess
2013-07-05 18:21 ` Pedro Alves
2013-07-08 10:22 ` Andrew Burgess
2013-07-09 9:54 ` Regression for implptr.exp and pieces.exp [Re: [COMMIT PATCH] value_bits_valid: Fix latent bug.] Jan Kratochvil
2013-07-09 14:16 ` Andrew Burgess [this message]
2013-07-24 20:10 ` Jan Kratochvil
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=51DC1B1A.5090203@broadcom.com \
--to=aburgess@broadcom.com \
--cc=gdb-patches@sourceware.org \
--cc=jan.kratochvil@redhat.com \
--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