On Tue, 18 May 2010 18:54:21 PDT David Leimbach <[email protected]> wrote: > > Were all of the binaries within recompiled against this code? Running 9vx > on my iMac is pretty smooth!
vx32/src/9vx.*.gz are the same as before (in case you are running those). Compiling 9vx on a MAC OS 10.6.3 required changing HOST_CC line in src/Makefrag to HOST_CC := $(CC) -fno-inline -m32 -D_XOPEN_SOURCE Undoubtedly there is a cleaner way. I copied vx32/src/9vx/syscalltrace/ to $home in 9vx and compiled syscalltrace there. term% 8.out -c /bin/echo Boo! 511 echo Brk 0x3233 0000b450 00000000 00000000 = 0 "" 0x11af077310cde470 0x11af077310d0da40 511 echo Pwrite 0x31d6 1 0000a458/"Boo!." 5 -0x1Boo! = 5 "" 0x11af07731e11e758 0x11af077326aed448 511 echo Open 0x32c0 00009ec0/"#c/pid" 00000000 = 3 "" 0x11af0773315f14c0 0x11af0773316790a0 511 echo Pread 0x3287 3 0fffff00/"........511." 20 -0x1 = 12 "" 0x11af07733f047958 0x11af07733f09cca0 511 echo Close 0x32ee 3 = 0 "" 0x11af07734a6dad78 0x11af07734a707c38 511 echo Exits 0x1bd5 0/""cwrite: /proc/511/syscall: failed 12 bytes: process exited tterm% Very nice! Is the the syscall trace data format easy to parse? If so it can be massaged in various ways.
