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/24870] gdb.lookup_type fails if a name is both a type and a variable Date: Fri, 01 Dec 2023 04:06:37 +0000 [thread overview] Message-ID: <bug-24870-4717-bLtgD3YyDG@http.sourceware.org/bugzilla/> (raw) In-Reply-To: <bug-24870-4717@http.sourceware.org/bugzilla/> https://sourceware.org/bugzilla/show_bug.cgi?id=24870 Tom Tromey <tromey at sourceware dot org> changed: What |Removed |Added ---------------------------------------------------------------------------- Ever confirmed|0 |1 Assignee|unassigned at sourceware dot org |tromey at sourceware dot org CC| |tromey at sourceware dot org Last reconfirmed| |2023-12-01 Status|UNCONFIRMED |NEW --- Comment #1 from Tom Tromey <tromey at sourceware dot org> --- This is fixed the symbol domain series. >>> gdb.lookup_type('foo') <gdb.Type code=TYPE_CODE_STRUCT name=foo> >>> gdb.lookup_global_symbol('foo', gdb.SYMBOL_VAR_DOMAIN).value() <gdb.Value object at 0x7fad14917410> >>> gdb.lookup_global_symbol('foo', gdb.SYMBOL_TYPE_DOMAIN).value() Traceback (most recent call last): File "<stdin>", line 1, in <module> TypeError: cannot get the value of a typedef -- You are receiving this mail because: You are on the CC list for the bug.
next prev parent reply other threads:[~2023-12-01 4:06 UTC|newest] Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top [not found] <bug-24870-4717@http.sourceware.org/bugzilla/> 2023-03-07 14:31 ` tromey at sourceware dot org 2023-12-01 4:06 ` tromey at sourceware dot org [this message] 2024-01-28 23:45 ` cvs-commit at gcc dot gnu.org 2024-01-28 23:45 ` tromey at sourceware dot org 2024-01-28 23:45 ` tromey at sourceware dot org
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-24870-4717-bLtgD3YyDG@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: linkBe 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).