On Sat, Sep 4, 2010 at 12:58 AM, Akshat Kumar <aku...@mail.nanosouffle.net> wrote: > Is ratrace usable on native Plan 9 (I understand it's in use on 9vx > thus far)? I don't see a /proc/n/syscall file for any of my processes; > is there some kernel patch for this?
One could take the modified version of my syscall tracing code that jmk put into the 9k kernel and put that into the regular plan 9 kernel. He did a very nice job of making it almost completely live in port and it's a good lesson in getting it right, worth looking at. Paper submitted to iwp9 ... I don't run any systems in my lab with the 9 kernel any more so I have not been motivated to make the change myself. I have used ratrace heavily on Blue Gene for debugging, and it's been much easier to use than Acid in that environment. I still use acid truss at times, when ratrace is not available, but I find ratrace far more useful when it is there. Actually, I now realize it's worse than that: I've stopped using systems that don't have ratrace because I find debugging problems without some sort of syscall trace to be too time-consuming. Note that it's easy to drop ratrace into scripts and that's handy. The getpid change I described here is now in my bitbucket repo https://rminn...@bitbucket.org/rminnich/sysfromiso That code builds and works on 9vx. I know there were some issues a few weeks ago with the builds which is why I mention it here. You should be able to build that userland code and run it on any Plan 9 system. I have built that tree to support arm, for example. The vx32 I am using is a combo of changes from yiyu and me and is found at https://rminn...@bitbucket.org/rminnich/vx32 ron
