This is the mail archive of the
gdb@sourceware.org
mailing list for the GDB project.
Re: recursion limit exceeded in Python API, but there's only one function in traceback
- From: Doug Evans <xdje42 at gmail dot com>
- To: Ãmer Sinan AÄacan <omeragacan at gmail dot com>
- Cc: paul_koning <Paul_Koning at dell dot com>, pmuldoon <pmuldoon at redhat dot com>, gdb <gdb at sourceware dot org>
- Date: Fri, 17 Oct 2014 09:40:58 -0700
- Subject: Re: recursion limit exceeded in Python API, but there's only one function in traceback
- Authentication-results: sourceware.org; auth=none
- References: <CAMQQO3knCrj=7dQNV1NEJofLhm7gZzvzG55K66uDOJt7qYrjGg at mail dot gmail dot com> <543FBDFF dot 3050709 at redhat dot com> <104DEFBD-D686-4290-8E3C-725A51C165E6 at dell dot com> <CAMQQO3=GxjGzF-9RXQsJ_9=Du3rS-UoYFA_0-friPp1nMa8yAA at mail dot gmail dot com> <7BB30632-15BE-4EF8-B84F-D35A27772F18 at dell dot com> <CAMQQO3kAPanS0uPPjUjiTFjpkOKUR5CiV55BJMbbA2p_J7d3nQ at mail dot gmail dot com> <CAMQQO3kehAHCMQkEOsU8kak5j=CdwZqKEy6_nHubWJF4F3A+Lg at mail dot gmail dot com>
On Fri, Oct 17, 2014 at 2:30 AM, Ãmer Sinan AÄacan <omeragacan@gmail.com> wrote:
> I'm still having this problem. I just tried this:
>
> def handler():
> gdb.execute("continue")
> print "continue returned"
>
> This doesn't print anything, until the script fails with "maximum
> recursion depth". Then it prints lots of "continue returned" lines.
>
> So the problem is `gdb.execute` doesn't immediately return and that's
> causing Python stack to grow, because GDB is calling this function
> without returning anything to previous calls.
One thing to keep in mind here is that gdb.execute is akin to typing
the command in at the (gdb) prompt.
IOW, if you as a user typed "continue" at the (gdb) prompt what would
you want to happen?
The definition of the "continue" command is that the inferior is
resumed until it stops and then the "continue" command completes.
> I think I need a version of `gdb.execute` that returns immediately.
> ie. async version or something like that. Is such a thing possible?
There is "continue &" for the case at hand.
There is no async version of gdb.execute itself.
Alas there is no corresponding "wait" command for "continue &" (I have
one in a sandbox that I get to when I'm able).
So once the inferior is running you've kinda lost programmatic control.
There is the "interrupt" command but it is broken in the sense that it
is implicitly async (the "&" is implicitly present).
I have a sandbox that fixes this too (getting this submitted tripped
over another gdb bug which I'm needing to fix first - a not uncommon
occurrence in gdb-land).
Other things come into play here like all-stop vs non-stop
https://sourceware.org/gdb/current/onlinedocs/gdb/Thread-Stops.html#Thread-Stops
but the async version of gdb.execute("continue") is gdb.execute("continue &").
Also note that resuming the inferior in a breakpoint handler is
supported, but further commands after the continue are not.
This isn't enforced in the python API, so I'm not sure what might
happen. Some things may work, others may not.
https://sourceware.org/gdb/current/onlinedocs/gdb/Break-Commands.html#Break-Commands