Chris Moller wrote:
Phil Muldoon wrote:
Roland McGrath wrote:
I think of the interface as asynchronous at base. There may at some
point be some synchronous calls to optimize the round trips. But we
know that by its nature an interface for handling many threads at once
has to be
Chris Moller wrote:
No guarantees, of course--the next-generation stuff may do things
differently--but even as I type this, I'm hacking together a
boilerplate framework that does exactly as described above.
Missed this in the last question, so apologies for the multiple emails.
When can I
Phil Muldoon wrote:
Chris Moller wrote:
No guarantees, of course--the next-generation stuff may do things
differently--but even as I type this, I'm hacking together a
boilerplate framework that does exactly as described above.
Missed this in the last question, so apologies for the multiple
Phil Muldoon wrote:
Thanks for the description Chris. From an ntrace client implementation
point of view, non-ordered replies to asynchronous requests present
an ordering conundrum in the client - especially as it scales to many
many inferiors.
I tend to think of the asynch stuff not as
Phil Muldoon wrote:
Chris Moller wrote:
Phil Muldoon wrote:
Thanks for the description Chris. From an ntrace client
implementation point of view, non-ordered replies to asynchronous
requests present an ordering conundrum in the client - especially as
it scales to many many inferiors.
Forgot to mention, BTW, there's a mini-app in utracer/*.[ch] that shows
the utracer API in use in a fake GTK-based debugger.
Phil Muldoon wrote:
Chris Moller wrote:
Phil Muldoon wrote:
Thanks for the description Chris. From an ntrace client
implementation point of view, non-ordered
Phil Muldoon wrote:
Roland McGrath wrote:
I think of the interface as asynchronous at base. There may at some
point be some synchronous calls to optimize the round trips. But we
know that by its nature an interface for handling many threads at once
has to be asynchronous, because an event
Here is a vague start at the directions I have in mind for a user-level
interface that I've been calling ntrace. It's not a real specific plan
at the literal interface level. It's an overview of what the components
are that the bit-level definition of the user-level interface sits atop.
I'll
