This is the mail archive of the
gdb-patches@sourceware.org
mailing list for the GDB project.
Re: beginnings of Guile support
- From: Doug Evans <dje at sceeck dot org>
- To: Phil Muldoon <pmuldoon at redhat dot com>
- Cc: gdb-patches at sourceware dot org
- Date: Mon, 9 Sep 2013 22:19:59 -0700
- Subject: Re: beginnings of Guile support
- Authentication-results: sourceware.org; auth=none
- References: <CAEei7h90tuXtBzVbNjtLQkv6ECA+EsdkYmt==MEMJcUf3m-bcA at mail dot gmail dot com> <522A0287 dot 40700 at redhat dot com>
On Fri, Sep 6, 2013 at 9:27 AM, Phil Muldoon <pmuldoon@redhat.com> wrote:
> I noticed you removed the conditional
> breakpoint check where only a Python "stop" callback can be attached
> to a breakpoint, or a "traditional" GDB condition. Your work is a
> work in progress, so I am not going to worry too much at the moment.
> But every "stop" callback attached to a breakpoint must be allowed to
> run, even if the a previous "stop" callback indicated True to stop, or
> a previous condition expression attached to GDB resolved to True. I
> guess we can look at this area again when your work is getting closer
> to submission.
Righto.
> Thanks for the preview. Are you aiming for 100% feature parity with
> the Python work? (IE, frame filters, etc)
100% feature parity isn't an aim per se.
I expect python to continue to evolve in its own way.
OTOH, I do want the scheme code to not be dissimilar without a good reason.