This is the mail archive of the
gdb-patches@sourceware.org
mailing list for the GDB project.
Re: [PING^3] [PATCH] Expose signal and syscall catchpoints to Python
- From: <Paul_Koning at Dell dot com>
- To: <brobecker at adacore dot com>
- Cc: <dje at google dot com>, <ale+gdb at clearmind dot me>, <gdb-patches at sourceware dot org>
- Date: Sat, 19 Dec 2015 18:17:17 +0000
- Subject: Re: [PING^3] [PATCH] Expose signal and syscall catchpoints to Python
- Authentication-results: sourceware.org; auth=none
- References: <001a1136affa52fa4b052730e695 at google dot com> <20151219035647 dot GH29928 at adacore dot 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