Date: Mon, 06 Nov 1995 17:41:58 -0500 From: Paul Fox <pgf@American.COM> To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch) Cc: freebsd-ports@freebsd.org Subject: Re: port of strace? Message-ID: <199511062241.RAA11840@mozart.american.com> In-Reply-To: j's message of Mon, 06 Nov 1995 23:03:41 %2B0100. <199511062203.XAA23399@uriah.heep.sax.de>
next in thread | previous in thread | raw e-mail | index | archive | help
> >
> > hi -- is anyone aware of a porting effort for the "strace" command?
>
> Hmm, we've got ktrace already. Where's the difference?
>
well, maybe my kdump isn't configured right, and please let me know
otherwise if i'm wrong, but i find the output of strace a lot easier to
grok. for example, strace shows me:
access("./myfile", R_OK) = -1 ENOENT (No such file or directory)
where kdump shows me:
CALL access(0xefbfd0c8,0x4)
NAMI "./myfile"
RET access 0
strace also seems to decode a lot more user-level stuff than kdump will --
here's what it shows for an fstat call (with "strace -v", which turns on
full dumping of "big" stuff):
fstat(4, {st_dev=makedev(7, 0), st_ino=5806, st_mode=S_IFREG|0644,
st_nlink=1, st_uid=0, st_gid=10, st_blksize=8192, st_blocks=8,
st_size=4096, st_atime=95/11/06-17:36:21, st_mtime=95/10/20-20:35:59,
st_ctime=95/10/20-20:36:00}) = 0
unless i'm missing something, kdump, on the other hand, gives
CALL fstat(0x1,0xefbfcd30)
RET fstat 0
now, as i said, i may not be using kdump correctly -- the man page implies
that it will fill in signal and errno values for me, but it's not doing that.
so there could well be some user error in here.
paul
---------------------
paul fox american internet corporation
pgf@american.com (home: pgf@foxharp.boston.ma.us)
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199511062241.RAA11840>