Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Doug Evans <dje@sceeck.org>
To: Phil Muldoon <pmuldoon@redhat.com>
Cc: gdb-patches@sourceware.org
Subject: Re: beginnings of Guile support
Date: Tue, 10 Sep 2013 05:20:00 -0000	[thread overview]
Message-ID: <CAEei7h8LOOJ7mmg06aQR2ThtcojoAG-oQ_MXf12vDyBMfc0UjQ@mail.gmail.com> (raw)
In-Reply-To: <522A0287.40700@redhat.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.


  reply	other threads:[~2013-09-10  5:20 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-09-06 15:35 Doug Evans
2013-09-06 16:27 ` Phil Muldoon
2013-09-10  5:20   ` Doug Evans [this message]
2013-09-09 21:09 ` Tom Tromey
2013-09-10  5:21   ` Doug Evans

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=CAEei7h8LOOJ7mmg06aQR2ThtcojoAG-oQ_MXf12vDyBMfc0UjQ@mail.gmail.com \
    --to=dje@sceeck.org \
    --cc=gdb-patches@sourceware.org \
    --cc=pmuldoon@redhat.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