[haiku-commits] Re: r39846 - in haiku/trunk: headers/os/kernel headers/private/debug headers/private/kernel src/kits/debug src/system/kernel ...
- From: Rene Gollent <anevilyak@xxxxxxxxx>
- To: haiku-commits@xxxxxxxxxxxxx
- Date: Tue, 14 Dec 2010 16:16:23 -0500
On Tue, Dec 14, 2010 at 3:42 PM, Ingo Weinhold <ingo_weinhold@xxxxxx> wrote:
> For the time being I'd start with team creation/deletion/exec and thread
> creation/deletion events. ATM the only programs interested in those events I
> can think of are Debugger (for the team window) and the registrar (to know
> when an application dies).
ProcessController as well. That begs the question though: would this
listener mechanism be in addition to the already-existing debug
interface for capturing those events or would it replace them? How
would they differ?
> Sure. OTOH since Debugger would be the only user of the interface, a polling
> approach implemented there would be just as acceptable.
I was hoping to avoid polling simply because the events I was
concerned with are fairly infrequent, so it seems wasteful to poll for
their results, especially as that can get potentially time consuming
in a larger/more complex app that might have a lot of threads alive in
its team. I guess you'd intend this as another type of debugger Job
that just gets submitted periodically?
Regards,
Rene
Other related posts:
