From: Eli Zaretskii <eliz@gnu.org>
To: Andrew Burgess <aburgess@broadcom.com>
Cc: gdb-patches@sourceware.org, jan.kratochvil@redhat.com
Subject: Re: PATCH: error reading variable: value has been optimized out
Date: Sat, 01 Sep 2012 08:17:00 -0000 [thread overview]
Message-ID: <83harip386.fsf@gnu.org> (raw)
In-Reply-To: <504092C0.2000602@broadcom.com>
> Date: Fri, 31 Aug 2012 11:32:32 +0100
> From: "Andrew Burgess" <aburgess@broadcom.com>
> cc: "Jan Kratochvil" <jan.kratochvil@redhat.com>
>
> On 26/08/2012 6:18 PM, Jan Kratochvil wrote:
> > I agree with the fix but it should have GDB-testsuite compatible testcase.
> > Also FYI it is only for backward compatibility with old GCCs.
>
> Included a test case (below) that covers 4 different cases, all of
> which are currently broken in different ways.
Thank you for doing this.
> [...] but as gcc is no longer creating examples like this I think we can accept the more limited solution I originally suggessted, if that's ok.
"No longer creating" since what version of GCC?
I don't think we should drop use cases just because they are only
possible on past (old) versions of GCC. GDB is not limited to debug
programs created only by latest GCC versions. I happen to still use a
very old version of GCC (because it is stable and fast, and because I
rarely need C++), and would very much like to have better debugging
abilities for optimized code than what I have now.
TIA
next prev parent reply other threads:[~2012-09-01 8:17 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-24 12:11 Andrew Burgess
2012-08-26 18:22 ` Jan Kratochvil
2012-08-27 15:46 ` Tom Tromey
2012-08-31 9:59 ` Eli Zaretskii
2012-09-03 15:07 ` Jan Kratochvil
2012-08-31 10:33 ` Andrew Burgess
2012-09-01 8:17 ` Eli Zaretskii [this message]
2012-09-03 8:32 ` Andrew Burgess
2012-09-03 11:24 ` Jan Kratochvil
2012-09-03 15:38 ` Eli Zaretskii
2012-09-03 15:17 ` Jan Kratochvil
2012-09-04 16:58 ` Andrew Burgess
2012-09-05 18:54 ` Jan Kratochvil
2012-09-12 17:30 ` Tom Tromey
2012-09-13 12:34 ` Andrew Burgess
2012-09-14 19:02 ` Tom Tromey
2012-09-14 21:39 ` Andrew Burgess
2012-09-17 16:57 ` Jan Kratochvil
2012-09-19 14:29 ` Andrew Burgess
2012-09-20 13:28 ` Jan Kratochvil
2012-09-21 17:19 ` Andrew Burgess
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=83harip386.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=aburgess@broadcom.com \
--cc=gdb-patches@sourceware.org \
--cc=jan.kratochvil@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