Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Jan Kratochvil <jan.kratochvil@redhat.com>
To: Tom Tromey <tromey@redhat.com>
Cc: gdb-patches@sourceware.org
Subject: Re: RFC: partially fix empty DW_OP_piece
Date: Fri, 04 Jun 2010 21:47:00 -0000	[thread overview]
Message-ID: <20100604214701.GA8886@host0.dyn.jankratochvil.net> (raw)
In-Reply-To: <m3k4qetr45.fsf@fleche.redhat.com>

On Fri, 04 Jun 2010 23:39:06 +0200, Tom Tromey wrote:
> >>>>> "Jan" == Jan Kratochvil <jan.kratochvil@redhat.com> writes:
> 
> Jan> OK, that probably means there really must remain a way to convert
> Jan> `inferior dependent struct value' into an `inferior independent
> Jan> struct value'.
> 
> Yeah, at least as far as the bounds are concerned.  IMO.
> 
> The current gdb model is sort of mixed.  A struct value is a snapshot of
> some bit of state.  But, when printing a value, we might refer to other
> state in the target.  For example:
> 
>     struct x { char *name; };

Understood but I find it more wrong in (plain) C as it has no `string' type.

The same problem happens for other data types being PythonPrettyPrinted.


Thanks,
Jan


  reply	other threads:[~2010-06-04 21:47 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-05-14  6:39 Tom Tromey
2010-05-14 22:51 ` Jan Kratochvil
2010-05-21 19:48   ` Tom Tromey
2010-06-01 17:34   ` Tom Tromey
2010-06-02 18:54     ` Jan Kratochvil
2010-06-02 20:07       ` Tom Tromey
2010-06-03 17:46         ` Jan Kratochvil
2010-06-04 19:05           ` Tom Tromey
2010-06-04 19:10             ` Jan Kratochvil
2010-06-04 21:39               ` Tom Tromey
2010-06-04 21:47                 ` Jan Kratochvil [this message]
2010-05-20 23:04 ` Joel Brobecker

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=20100604214701.GA8886@host0.dyn.jankratochvil.net \
    --to=jan.kratochvil@redhat.com \
    --cc=gdb-patches@sourceware.org \
    --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