On Tue, 2003-07-15 at 09:09, Terry Lambert wrote: > > One way to track this down, if it's that repeatable for everyone, > would be to open another terminal window, get the pid of the > program that's going to do this, and then: > > truss -p <pid> | grep "Resource temp" > > ...or just let it run to completion, and you'll get some context, > too, in your scrollback buffer.
Being the curious person that I am, I tried the following from the truss
manpage :
% truss /bin/echo hello
truss: cannot open /proc/1805/mem: No such file or directory
truss: cannot open /proc/curproc/mem: No such file or directory
Is this expected behaviour on -CURRENT or is it just me? More
information :
% ls -al /proc
total 4
dr-xr-xr-x 2 root wheel 512 Jan 16 22:26 .
drwxr-xr-x 17 root wheel 512 Jul 11 18:46 ..
% file `which truss`
/usr/bin/truss: ELF 32-bit LSB executable, Intel 80386, version 1
(FreeBSD), for FreeBSD 5.0.1, dynamically linked (uses shared libs),
stripped
% uname -a
FreeBSD nemesis.work 5.1-RELEASE FreeBSD 5.1-RELEASE #5: Fri Jun 27
12:52:43 SAST 2003 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/NEMESIS
i386
--
byron
Bus error -- driver executed.
signature.asc
Description: This is a digitally signed message part
