From owner-freebsd-ports Mon Nov 6 14:49:35 1995 Return-Path: owner-ports Received: (from root@localhost) by freefall.freebsd.org (8.6.12/8.6.6) id OAA17305 for ports-outgoing; Mon, 6 Nov 1995 14:49:35 -0800 Received: from mail.barrnet.net (mail.barrnet.net [131.119.246.7]) by freefall.freebsd.org (8.6.12/8.6.6) with ESMTP id OAA17286 for ; Mon, 6 Nov 1995 14:48:59 -0800 Received: from mozart.american.com (mozart.american.com [204.253.96.2]) by mail.barrnet.net (8.7.1/MAIL-RELAY-LEN) with SMTP id OAA24332 for ; Mon, 6 Nov 1995 14:45:15 -0800 (PST) Received: from localhost (localhost [127.0.0.1]) by mozart.american.com (8.6.12/8.6.9) with SMTP id RAA11840; Mon, 6 Nov 1995 17:41:59 -0500 Message-Id: <199511062241.RAA11840@mozart.american.com> X-Authentication-Warning: mozart.american.com: Host localhost didn't use HELO protocol To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch) Subject: Re: port of strace? In-reply-to: j's message of Mon, 06 Nov 1995 23:03:41 +0100. <199511062203.XAA23399@uriah.heep.sax.de> Cc: freebsd-ports@freebsd.org Reply-to: pgf@American.COM Date: Mon, 06 Nov 1995 17:41:58 -0500 From: Paul Fox Sender: owner-ports@freebsd.org Precedence: bulk > > > > 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)