From: Jan Kratochvil <jan.kratochvil@redhat.com>
To: Pedro Alves <pedro@codesourcery.com>
Cc: gdb-patches@sourceware.org, Tom Tromey <tromey@redhat.com>
Subject: Re: [patch] Fix internal error on optimized-out values (regression by me)
Date: Wed, 12 Oct 2011 20:33:00 -0000 [thread overview]
Message-ID: <20111012203329.GA23721@host1.jankratochvil.net> (raw)
In-Reply-To: <201110102240.28440.pedro@codesourcery.com>
On Mon, 10 Oct 2011 23:40:28 +0200, Pedro Alves wrote:
> IMO, this is just like "p s.f", printing <unavailable> when the whole
> of `s' is unavailable. From the unavailable.exp test:
>
> print globalstruct.memberf
> $7 = <unavailable>
> (gdb) PASS: gdb.trace/unavailable.exp: collect globals: print globalstruct.memberf
> print globalstruct.memberd
> print globalstruct
> $9 = {memberc = <unavailable>, memberi = <unavailable>, memberf = <unavailable>, memberd = <unavailable>}
>
> It just happens that today, we only support either wholy
> optimized-out values, or wholly not optimized-out values.
This would suggest the user-visible behavior should be more the former patch:
http://sourceware.org/ml/gdb-patches/2011-09/msg00449.html
printing <optimized out>
In either patch case when partially-<optimized out> values get implemented the
code needs to be changed anyway.
> and that ((struct) <optimized out>).field will need to be able to be
> <optimized out>.
Yes.
Thanks,
jan
next prev parent reply other threads:[~2011-10-12 20:33 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-26 19:26 Jan Kratochvil
2011-09-27 13:41 ` Jan Kratochvil
2011-10-03 19:34 ` Tom Tromey
2011-10-10 20:54 ` Jan Kratochvil
2011-10-10 21:40 ` Pedro Alves
2011-10-11 17:33 ` Tom Tromey
2011-10-12 20:11 ` Jan Kratochvil
2011-10-13 15:18 ` Tom Tromey
2011-10-13 16:36 ` Jan Kratochvil
2011-10-12 20:33 ` Jan Kratochvil [this message]
2011-10-13 15:27 ` Pedro Alves
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=20111012203329.GA23721@host1.jankratochvil.net \
--to=jan.kratochvil@redhat.com \
--cc=gdb-patches@sourceware.org \
--cc=pedro@codesourcery.com \
--cc=tromey@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