public inbox for gdb-prs@sourceware.org
help / color / mirror / Atom feed
From: "tromey at sourceware dot org" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug python/22686] gdb.lookup_type fails for array types
Date: Tue, 07 Mar 2023 14:34:06 +0000 [thread overview]
Message-ID: <bug-22686-4717-SWwh2Ts6gT@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-22686-4717@http.sourceware.org/bugzilla/>
https://sourceware.org/bugzilla/show_bug.cgi?id=22686
Tom Tromey <tromey at sourceware dot org> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |tromey at sourceware dot org
--- Comment #7 from Tom Tromey <tromey at sourceware dot org> ---
Bug 11797 suggests a new 'parse_type' function that applies
the language's type-parsing rules. This is more or less
what 'ptype' does, with the caveat being that ptype really
accepts any expression and yields its type, which can be
resolved in favor of parsing as if the string were an expression
if there is some ambiguity. What would be really better is
a separate "type" entry point to the parsers.
--
You are receiving this mail because:
You are on the CC list for the bug.
parent reply other threads:[~2023-03-07 14:34 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <bug-22686-4717@http.sourceware.org/bugzilla/>]
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=bug-22686-4717-SWwh2Ts6gT@http.sourceware.org/bugzilla/ \
--to=sourceware-bugzilla@sourceware.org \
--cc=gdb-prs@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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).