From: Phil Muldoon <pmuldoon@redhat.com>
To: "Doug Evans" <xdje42@gmail.com>,
"Ömer Sinan Ağacan" <omeragacan@gmail.com>
Cc: paul_koning <Paul_Koning@dell.com>, gdb <gdb@sourceware.org>
Subject: Re: recursion limit exceeded in Python API, but there's only one function in traceback
Date: Fri, 17 Oct 2014 17:35:00 -0000 [thread overview]
Message-ID: <5441534A.60009@redhat.com> (raw)
In-Reply-To: <CAP9bCMQA30LhOz58UNGvF78kShnLGK33=i6rHjhLmO8mP2D3Qg@mail.gmail.com>
On 17/10/14 17:40, Doug Evans wrote:
> 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
Yeah we can't police it only document it right now. Until Python has
discrete control of the inferior (instead of issuing commands through
gdb.execute) we would have to parse the code looking for "forbidden"
operations. That's a deep dark hole to go into. ;)
Hopefully one day when Guile and/or Python have rich and discrete
inferior control we could better police what the user should or should
not do at various states.
Cheers
Phil
next prev parent reply other threads:[~2014-10-17 17:35 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-16 10:46 Ömer Sinan Ağacan
2014-10-16 12:45 ` Phil Muldoon
2014-10-16 14:28 ` Paul_Koning
[not found] ` <CAMQQO3=GxjGzF-9RXQsJ_9=Du3rS-UoYFA_0-friPp1nMa8yAA@mail.gmail.com>
2014-10-16 15:04 ` Paul_Koning
2014-10-16 15:15 ` Ömer Sinan Ağacan
2014-10-16 15:18 ` Ömer Sinan Ağacan
2014-10-17 9:31 ` Ömer Sinan Ağacan
2014-10-17 10:11 ` Phil Muldoon
2014-10-17 10:53 ` Ömer Sinan Ağacan
2014-10-17 14:20 ` Phil Muldoon
2014-10-17 14:27 ` Ömer Sinan Ağacan
2014-10-17 15:02 ` Phil Muldoon
2014-10-17 15:04 ` Paul_Koning
2014-10-17 17:31 ` Phil Muldoon
2014-10-17 16:41 ` Doug Evans
2014-10-17 17:35 ` Phil Muldoon [this message]
2014-10-17 16:45 ` Doug Evans
[not found] ` <543FE072.6040507@redhat.com>
2014-10-16 15:16 ` Ömer Sinan Ağacan
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=5441534A.60009@redhat.com \
--to=pmuldoon@redhat.com \
--cc=Paul_Koning@dell.com \
--cc=gdb@sourceware.org \
--cc=omeragacan@gmail.com \
--cc=xdje42@gmail.com \
/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