On Fri, Sep 14, 2001 at 11:39:19AM -0700, [EMAIL PROTECTED] wrote:
> My work is to come up with a "trace/replay" framework and an
> extensible system for tracing, tuning, *debugging* and steering
>
> rpctrace does the first part of it partially. rpctrace code will help
> me kick start my work.
>
> In tracing alone, I need to timestamp (,probably filter) and record
> the messages for later replaying
I see. I don't know if it is a good idea to put hooks in libports, though.
Not all ports are managed by it, so you will miss RPCs if you just
do it there, and anyway I think it is not very elegant.
Maybe you can put something in rpctrace that makes it communicate with
a master serv that collects messages from several tasks... but that's just
an idea, I haven't thought that through. As you need a master server
anyway, and there is already the logic to intercept rpcs in rpctrace.
Thanks,
Marcus
--
`Rhubarb is no Egyptian god.' Debian http://www.debian.org [EMAIL PROTECTED]
Marcus Brinkmann GNU http://www.gnu.org [EMAIL PROTECTED]
[EMAIL PROTECTED]
http://www.marcus-brinkmann.de
_______________________________________________
Bug-hurd mailing list
[EMAIL PROTECTED]
http://mail.gnu.org/mailman/listinfo/bug-hurd
