Hello! On Wed, Mar 21, 2007 at 08:09:31AM +0100, [EMAIL PROTECTED] wrote: > Implementing the possibility of attaching rpctrace to running processes, > is one possible thing that could be done. But there are many others, > like adding ability to rpctrace to show the names of the parameters > (needs rpctrace and mig changes); adding some tool(s) that allow logging > the interactions between several processes, to help understanding > complex problems and/or doing system profiling; interactive RPC > debugging tools (possibly as GDB extension); and so on. > > However, I didn't propose this so far, as tschwinge seems to have a > perfectly opposite opinion than me on what are suitable tasks and what > aren't.
Huh, what's that? In fact, what I told you was that I wouldn't know how to wrap what you suggested into a concise wording for a GSoC task, so that someone who isn't familiar with all those Hurd details would know what this task was about. I then asked you to come up with such a wording to then install that task, but, so far, you didn't respond to that plea and instead now accuse me to not consider your ideas worthwhile? That doesn't fit. I mean, these are tasks that require a really intimate knowledge of how the components of a Hurd system interact with each other. That's not something where an ``average student'' could make any sense of. That's at least my opinion on this matter. Regards, Thomas
signature.asc
Description: Digital signature
_______________________________________________ Bug-hurd mailing list Bug-hurd@gnu.org http://lists.gnu.org/mailman/listinfo/bug-hurd
