This is the mail archive of the
gdb-patches@sourceware.org
mailing list for the GDB project.
Re: PATCH: error reading variable: value has been optimized out
- From: Tom Tromey <tromey at redhat dot com>
- To: "Andrew Burgess" <aburgess at broadcom dot com>
- Cc: "gdb-patches\ at sourceware dot org" <gdb-patches at sourceware dot org>, "Jan Kratochvil" <jan dot kratochvil at redhat dot com>
- Date: Fri, 14 Sep 2012 13:02:19 -0600
- Subject: Re: PATCH: error reading variable: value has been optimized out
- References: <50376F3B.1080407@broadcom.com> <20120826171840.GA21205@host2.jankratochvil.net> <504092C0.2000602@broadcom.com> <87wqzz5eug.fsf@fleche.redhat.com> <5051D2A7.2000009@broadcom.com>
>>>>> "Andrew" == Andrew Burgess <aburgess@broadcom.com> writes:
Tom> If it is just a theoretical problem I think we can just declare it
Tom> unsupported; and, if we do see it, try reporting it as a compiler bug
Tom> first. After all, the compiler could just emit an empty piece instead.
Andrew> I'm happy to mark these tests as unsupported. As the tests (#2
Andrew> -> #4) are pretty much zero cost given that I'm adding test #1
Andrew> anyway I'd like to leave them in. I've created a new patch, the
Andrew> only change is that test #3 and #4 now report unsupported (with
Andrew> comment), and test #2 reports pass, with a comment to explain
Andrew> the reasoning.
Andrew> + # If we ever fix gdb so this passes we should delete the
Andrew> + # unsupported case below.
Andrew> + xpass $test
Andrew> + unsupported $test
I think these tests should 'pass' if they generate the correct output,
and 'kfail' otherwise.
Tom