From: Paul Bolle <pebolle@tiscali.nl>
To: gdb-patches@sourceware.org
Subject: [PATCH] [RFC] python: gdb.Type: strip typedefs past pointers too
Date: Sat, 18 Sep 2010 14:12:00 -0000 [thread overview]
Message-ID: <1284753356.21566.10.camel@localhost.localdomain> (raw)
0) gdb.Type.strip_typedefs() stops stripping types if it encounters a
type that is a pointer to a typedef:
(gdb) ptype wchar_t
type = long int
(gdb) ptype wchar_t *
type = long int *
(gdb) python print gdb.lookup_type("wchar_t").strip_typedefs()
long int
(gdb) python print gdb.lookup_type("wchar_t").pointer().strip_typedefs()
wchar_t *
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 *
(gdb) python print gdb.lookup_type("wchar_t").strip_typedefs()
long int
(gdb) python print gdb.lookup_type("wchar_t").pointer().strip_typedefs()
long int *
2) I'm not comfortable with the code I'm using here (ie, gdb's type
handling code) so I'd appreciate comments on this draft patch.
Paul Bolle
---
Currently gdb.Type.strip_typedefs() doesn't strip typedefs if it
encounters a type that is a pointer to a typedef. In those cases it
doesn't really behave as advertised (well, as I understand the
advertisement).
So learn strip_typedefs() to handle pointers to typedefs too.
---
gdb/python/py-type.c | 23 ++++++++++++++++++++++-
1 files changed, 22 insertions(+), 1 deletions(-)
diff --git a/gdb/python/py-type.c b/gdb/python/py-type.c
index 8232436..08602a1 100644
--- a/gdb/python/py-type.c
+++ b/gdb/python/py-type.c
@@ -267,8 +267,29 @@ static PyObject *
typy_strip_typedefs (PyObject *self, PyObject *args)
{
struct type *type = ((type_object *) self)->type;
+ struct type *real_type;
+ int level = 0;
- return type_to_type_object (check_typedef (type));
+ real_type = check_typedef (type);
+
+ while (TYPE_CODE (real_type) == TYPE_CODE_PTR ||
+ TYPE_CODE (real_type) == TYPE_CODE_TYPEDEF)
+ {
+ if (TYPE_CODE (real_type) == TYPE_CODE_TYPEDEF)
+ {
+ CHECK_TYPEDEF (real_type);
+ }
+ else
+ {
+ real_type = TYPE_TARGET_TYPE (real_type);
+ level++;
+ }
+ }
+
+ while (level--)
+ real_type = lookup_pointer_type (real_type);
+
+ return type_to_type_object (real_type);
}
/* Return an array type. */
--
1.7.2.3
next reply other threads:[~2010-09-17 19:56 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-18 14:12 Paul Bolle [this message]
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
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=1284753356.21566.10.camel@localhost.localdomain \
--to=pebolle@tiscali.nl \
--cc=gdb-patches@sourceware.org \
/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