From mboxrd@z Thu Jan 1 00:00:00 1970 MIME-Version: 1.0 Date: Tue, 18 May 2010 17:22:58 -0700 Message-ID: From: ron minnich To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net> Content-Type: text/plain; charset=ISO-8859-1 Subject: [9fans] system call trace version of 9vx available. Topicbox-Message-UUID: 269d6cbe-ead6-11e9-9d60-3106f5b1d025 http://bitbucket.org/rminnich/vx32 this is my hack of vx32. It includes a ram block device, but more importantly, it supports the system call trace code. In the 'root' of the repo is the syscalltrace directory; cd in there to make the syscalltrace binary. Comments and improvements welcome. Noah wrote the first version of syscalltrace.c. Thanks to Russ for suggestions that led to substantial improvements in the code; it's still not good enough (Jim McKie made a really great improvement which you can see in the 9k kernel) and I don't think it yet belongs in the main vx32 tree. That said, you can get a *lot* of work done with this version, and we've found syscalltrace very helpful on the bg/p effort, so I wanted to make sure people could see it. I've seen questions go by on this list lately that use of syscalltrace might have answered. I use syscalltrace all the time now when I hit a problem I don't understand. It would be helpful for those debugging cpu and auth problems, I think. Thanks to Russ, Jim, and Noah for their help and improvements. Any errors are mine. ron