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 mi/31063] Feature request: print raw types/omit types in -var-list-children Date: Fri, 16 Feb 2024 04:53:35 +0000 [thread overview] Message-ID: <bug-31063-4717-TzTVdOY0NQ@http.sourceware.org/bugzilla/> (raw) In-Reply-To: <bug-31063-4717@http.sourceware.org/bugzilla/> https://sourceware.org/bugzilla/show_bug.cgi?id=31063 --- Comment #3 from Tom Tromey <tromey at sourceware dot org> --- If you're using MI, then AFAIK varobj is the way to go. I just mean, the varobj code is kind of gross and some parts of the design are bad; and nobody really works actively on it. You could maybe get away with custom Python commands now. We pretty much took that approach for DAP. -- You are receiving this mail because: You are on the CC list for the bug.
prev parent reply other threads:[~2024-02-16 4:53 UTC|newest] Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-11-13 14:33 [Bug mi/31063] New: " dmitry.neverov at jetbrains dot com 2023-11-14 2:51 ` [Bug mi/31063] " tromey at sourceware dot org 2023-11-14 9:46 ` dmitry.neverov at jetbrains dot com 2024-02-16 4:53 ` tromey at sourceware dot org [this message]
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-31063-4717-TzTVdOY0NQ@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).