Hi, On Thu, Mar 22, 2007 at 10:50:49AM +0000, Tim Retout wrote: > On Wed, 2007-03-21 at 08:09 +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. > > These are all good ideas. The difficulty is, the SoC lasts only three > months, and "most students need the first month just to get their > bearings and actually start producing code".[0] It's important to > choose a project/set of tasks that fit within that timeframe. I > personally would be hesitant about trying to write a whole new > debugging tool over the summer - even with a good mentor. Well, it depends on the student. I can imagine that *some* would be able to create such a tool in three months, so I think it's not wrong to list it as a possibility -- as long as it's clear that the student is also free to choose some of the simpler suggestions. -antrik- _______________________________________________ Bug-hurd mailing list Bug-hurd@gnu.org http://lists.gnu.org/mailman/listinfo/bug-hurd
