[Bug python/27141] New: [RFE] Getting a python-call result is overly complicated

["hi-angel at yandex dot ru" <sourceware-bugzilla@sourceware.org>]

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

            Bug ID: 27141
           Summary: [RFE] Getting a python-call result is overly
                    complicated
           Product: gdb
           Version: 10.1
            Status: UNCONFIRMED
          Severity: normal
          Priority: P2
         Component: python
          Assignee: unassigned at sourceware dot org
          Reporter: hi-angel at yandex dot ru
  Target Milestone: ---

Unless I'm missing something, the only way to get a return value from python is
to write a whole separate class with two methods.¹ This is unwieldy and hinders
quick scripting.

For example, right now I want to set `commands` to a breakpoint so the debugee
gets only paused when there's a certain string somewhere in the `bt` command.
Well, the check is really easy to script up:

    py 'my_string' in gdb.execute('bt', to_string=True)

But then if I execute it as part of gdb "if" statement, I'll get

    No symbol "py" in current context.

Having to write a whole "convenience" function means not only a redundant text,
but also a need to debug it. Also, if one has to debug it in the current
session, my experience says that unless they already know how it works, they
might screw up the current session (that's what happened to me back when I was
trying to make pretty-printers work with no experience on them)

So, it would be really helpful to either teach `py` and/or `pi` calls to return
values, so they can be executed as part of any other GDB command chain, or to
introduce a new (a `p1`?) call for that purpose.

1: https://sourceware.org/gdb/current/onlinedocs/gdb/Functions-In-Python.html

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