public inbox for gdb-prs@sourceware.org help / color / mirror / Atom feed
From: "lxmachine at gmail dot com" <sourceware-bugzilla@sourceware.org> To: gdb-prs@sourceware.org Subject: [Bug python/13326] New: Need support for C++ method call for a gdb.Value object from within python Date: Thu, 20 Oct 2011 05:14:00 -0000 [thread overview] Message-ID: <bug-13326-4717@http.sourceware.org/bugzilla/> (raw) http://sourceware.org/bugzilla/show_bug.cgi?id=13326 Bug #: 13326 Summary: Need support for C++ method call for a gdb.Value object from within python Product: gdb Version: 7.3 Status: NEW Severity: normal Priority: P2 Component: python AssignedTo: unassigned@sourceware.org ReportedBy: lxmachine@gmail.com Classification: Unclassified The python scripting support is great. There is support for function call if a gdb.Value object is of type TYPE_CODE_FUNC. There is no support for method call yet if a gdb.Value object is of type TYPE_CODE_METHOD. In order to support the pretty-pritters for some classes, sometimes we need to call an method instead of just accessing some member fields. Thanks, Xun -- Configure bugmail: http://sourceware.org/bugzilla/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
next reply other threads:[~2011-10-20 5:14 UTC|newest] Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top 2011-10-20 5:14 lxmachine at gmail dot com [this message] 2012-05-05 20:13 ` [Bug python/13326] " vmiklos at frugalware dot org 2013-02-25 17:42 ` tfogal at alumni dot unh.edu 2021-01-21 19:27 ` malcolm.parsons at gmail dot com 2021-08-12 19:24 ` jwakely.gcc at gmail dot com 2023-07-24 16:30 ` joelhock at gmail dot com 2023-12-15 16:11 ` ssbssa at sourceware dot org 2024-02-08 19:10 ` cvs-commit at gcc dot gnu.org 2024-02-08 19:13 ` ssbssa 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-13326-4717@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).