[Bug python/27000] gdb.block_for_pc should accept a gdb.Value argument

["cvs-commit at gcc dot gnu.org" <sourceware-bugzilla@sourceware.org>]

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

--- Comment #5 from cvs-commit at gcc dot gnu.org <cvs-commit at gcc dot gnu.org> ---
The master branch has been updated by Tom Tromey <tromey@sourceware.org>:

https://sourceware.org/git/gitweb.cgi?p=binutils-gdb.git;h=d19ca0b35c9536210c5e8bd30504489b7439f51f

commit d19ca0b35c9536210c5e8bd30504489b7439f51f
Author: Tom Tromey <tom@tromey.com>
Date:   Sun Jun 5 07:42:12 2022 -0600

    Accept gdb.Value in more Python APIs

    PR python/27000 points out that gdb.block_for_pc will accept a Python
    integer, but not a gdb.Value.  This patch corrects this oversight.

    I looked at all uses of GDB_PY_LLU_ARG and fixed these up to use
    get_addr_from_python instead.  I also looked at uses of GDB_PY_LL_ARG,
    but those seemed relatively unlikely to be useful with a gdb.Value, so
    I didn't change them.  My thinking here is that a Value will typically
    come from inferior memory, and something like a line number is not too
    likely to be found this way.

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

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