public inbox for gdb-prs@sourceware.org
help / color / mirror / Atom feed
From: "ssbssa at sourceware dot org" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug python/13326] Need support for C++ method call for a gdb.Value object from within python
Date: Mon, 03 Jun 2024 15:26:30 +0000	[thread overview]
Message-ID: <bug-13326-4717-nKey69PR6c@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-13326-4717@http.sourceware.org/bugzilla/>

https://sourceware.org/bugzilla/show_bug.cgi?id=13326

--- Comment #7 from Hannes Domani <ssbssa at sourceware dot org> ---
(In reply to vuvova from comment #1)
> Same for TYPE_CODE_INTERNAL_FUNCTION:
> 
> (gdb) pi a=gdb.parse_and_eval('$_streq')
> (gdb) pi print a.type.code == gdb.TYPE_CODE_INTERNAL_FUNCTION
> True
> (gdb) pi a("1","2")
> Python Exception <type 'exceptions.RuntimeError'> Value is not callable (not
> TYPE_CODE_FUNC).:

Now this is fixed as well.

-- 
You are receiving this mail because:
You are on the CC list for the bug.

      parent reply	other threads:[~2024-06-03 15:26 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-10-20  5:14 [Bug python/13326] New: " lxmachine at gmail dot com
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
2024-06-03 15:19 ` cvs-commit at gcc dot gnu.org
2024-06-03 15:26 ` ssbssa 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-13326-4717-nKey69PR6c@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).