From: <Paul_Koning@Dell.com>
To: <brobecker@adacore.com>
Cc: <dje@google.com>, <ale+gdb@clearmind.me>, <gdb-patches@sourceware.org>
Subject: Re: [PING^3] [PATCH] Expose signal and syscall catchpoints to Python
Date: Sat, 19 Dec 2015 18:17:00 -0000 [thread overview]
Message-ID: <BEDBA4F6-E5D9-41DA-B491-8226111BD372@dell.com> (raw)
In-Reply-To: <20151219035647.GH29928@adacore.com>
> On Dec 18, 2015, at 10:56 PM, Joel Brobecker <brobecker@adacore.com> wrote:
>
>> This will need doc additions too of course, but before you
>> spend time on that there is a high level issue that we
>> (the community) should decide on:
>> Is it time to start subclassing breakpoints instead of
>> continually extending the one uber-breakpoint class?
>> IOW, should catchpoints be a subclass of breakpoints?
>>
>> Subclassing is clearly a better way to go,
>> so I'm kinda thinking now's the time.
>
> Thinking out loud...
>
> I like the idea of starting subclassing.
Same here.
That makes me wonder: it probably makes no sense for some of the classes, but there are likely to be some GDB classes where user-defined subclasses would be useful.
paul
next prev parent reply other threads:[~2015-12-19 18:17 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-18 19:11 Doug Evans
2015-12-19 3:56 ` Joel Brobecker
2015-12-19 18:17 ` Paul_Koning [this message]
-- strict thread matches above, loose matches on Subject: below --
2015-12-16 22:24 Alessandro Di Federico
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=BEDBA4F6-E5D9-41DA-B491-8226111BD372@dell.com \
--to=paul_koning@dell.com \
--cc=ale+gdb@clearmind.me \
--cc=brobecker@adacore.com \
--cc=dje@google.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