From: Andrew Burgess <andrew.burgess@embecosm.com>
To: gdb-patches@sourceware.org
Subject: Re: PING! Re: [PATCH 0/3] Make python/guile api catchpoint aware
Date: Fri, 25 Jun 2021 18:26:11 +0100 [thread overview]
Message-ID: <20210625172611.GN2568@embecosm.com> (raw)
In-Reply-To: <20210621120535.GD2568@embecosm.com>
* Andrew Burgess <andrew.burgess@embecosm.com> [2021-06-21 13:05:35 +0100]:
> I'm planning to push this patch later this week.
I've now pushed this series.
Thanks,
Andrew
>
> I think this is a first step to closing a hole in our
> breakpoint/catchpoint API, and when we look at how
> breakpoints/watchpoints are handled, this is the obvious approach.
>
> If anyone objects, feel free to say.
>
> Thanks,
> Andrew
>
>
> * Andrew Burgess <andrew.burgess@embecosm.com> [2021-06-01 12:04:19 +0100]:
>
> > Ping!
> >
> > Any thoughts?
> >
> > Thanks,
> > Andrew
> >
> > * Andrew Burgess <andrew.burgess@embecosm.com> [2021-05-12 14:04:57 +0100]:
> >
> > > This is a first, small step, towards adding catchpoint support to the
> > > python/guile apis.
> > >
> > > The first patch in this series has been posted before, but is repeated
> > > here as the second patch depends on it.
> > >
> > > ---
> > >
> > > Andrew Burgess (3):
> > > gdb/guile: improve the errors when creating breakpoints
> > > gdb/guile: allow for catchpoint type breakpoints in guile
> > > gdb/python: allow for catchpoint type breakpoints in python
> > >
> > > gdb/ChangeLog | 21 ++++++++
> > > gdb/NEWS | 4 ++
> > > gdb/doc/ChangeLog | 10 ++++
> > > gdb/doc/guile.texi | 4 ++
> > > gdb/doc/python.texi | 7 +++
> > > gdb/guile/scm-breakpoint.c | 19 ++++++-
> > > gdb/python/py-breakpoint.c | 6 ++-
> > > gdb/testsuite/ChangeLog | 14 +++++
> > > gdb/testsuite/gdb.guile/scm-breakpoint.exp | 44 ++++++++++++++++
> > > gdb/testsuite/gdb.python/py-breakpoint.c | 14 +++++
> > > gdb/testsuite/gdb.python/py-breakpoint.exp | 60 ++++++++++++++++++++++
> > > 11 files changed, 200 insertions(+), 3 deletions(-)
> > >
> > > --
> > > 2.25.4
> > >
prev parent reply other threads:[~2021-06-25 17:26 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-12 13:04 Andrew Burgess
2021-05-12 13:04 ` [PATCH 1/3] gdb/guile: improve the errors when creating breakpoints Andrew Burgess
2021-05-12 13:04 ` [PATCH 2/3] gdb/guile: allow for catchpoint type breakpoints in guile Andrew Burgess
2021-05-12 13:17 ` Eli Zaretskii
2021-05-12 13:05 ` [PATCH 3/3] gdb/python: allow for catchpoint type breakpoints in python Andrew Burgess
2021-05-12 13:18 ` Eli Zaretskii
2021-06-01 11:04 ` [PATCH 0/3] Make python/guile api catchpoint aware Andrew Burgess
2021-06-21 12:05 ` PING! " Andrew Burgess
2021-06-25 17:26 ` Andrew Burgess [this message]
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=20210625172611.GN2568@embecosm.com \
--to=andrew.burgess@embecosm.com \
--cc=gdb-patches@sourceware.org \
/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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).