Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Jan Kratochvil <jan.kratochvil@redhat.com>
To: Paul Bolle <pebolle@tiscali.nl>
Cc: gdb-patches@sourceware.org
Subject: Re: [PATCH] [RFC] python: gdb.Type: strip typedefs past pointers too
Date: Mon, 20 Sep 2010 12:02:00 -0000	[thread overview]
Message-ID: <20100920100417.GA5751@host1.dyn.jankratochvil.net> (raw)
In-Reply-To: <1284753356.21566.10.camel@localhost.localdomain>

On Fri, 17 Sep 2010 21:55:56 +0200, Paul Bolle wrote:
> 1) I drafted a patch (pasted below this message) that works around this
> limitation:
> 
> (gdb) ptype wchar_t
> type = long int
> (gdb) ptype wchar_t *
> type = long int *

What is the goal of this patch?  strip_typedefs I understand to be the Python
interface to check_typedef.

check_typedef is there to prepare whatever type you get to a point where you
have something you can process as pointer/array/integer/etc. It also sets type
sizeof of the outer typedef to sizeof of the resolved inner type for opaque
types, depending on how they got resolved.  With VLA patch the resolved size
also depends on the current/variable size.

I still do not see a use case why is it useful to resolve typedefs in the
inner sub-types.  Some functions will call check_typedef again while
recursively processing the type anyway.  What is your use case?

The strip_typedefs description should be fixed anyway as the text is now
ambiguous.


Regards,
Jan


  parent reply	other threads:[~2010-09-20 10:04 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-09-18 14:12 Paul Bolle
2010-09-19 16:35 ` Joel Brobecker
2010-09-19 17:56   ` Paul Bolle
2010-09-20  9:32     ` Daniel Jacobowitz
2010-09-20  9:48       ` Paul Bolle
2010-09-20 10:04         ` Daniel Jacobowitz
2010-09-20 10:15 ` Phil Muldoon
2010-09-20 10:53   ` Paul Bolle
2010-09-20 12:02 ` Jan Kratochvil [this message]
2010-09-20 16:25   ` Paul Bolle
2010-09-20 13:59     ` Paul Bolle
2010-09-20 16:08     ` Paul Bolle
2010-09-21 12:39     ` Jan Kratochvil
2010-09-20 13:14 ` André Pönitz

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=20100920100417.GA5751@host1.dyn.jankratochvil.net \
    --to=jan.kratochvil@redhat.com \
    --cc=gdb-patches@sourceware.org \
    --cc=pebolle@tiscali.nl \
    /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