Date: Fri, 17 Sep 2010 21:55:26 +0200 From: Norberto Lopes <nlopes.ml@gmail.com> To: freebsd-current@freebsd.org Cc: netchild@freebsd.org Subject: Extend ktrace/kdump output Message-ID: <8C5C36F5-A070-4CBA-8B8C-6751F8D636E1@gmail.com>
next in thread | raw e-mail | index | archive | help
Hi. I've been taking a look at ktrace and kdump in order to get (1) familiar = with the sources and (2) to finally try to give back something to the = community. So far from what I've seen, and after reading this thread = http://lists.freebsd.org/pipermail/freebsd-arch/2006-April/005107.html = it seems that most of those points got done. To warm up I changed the output of the stat structure in order to = provide me with the device name (something I actually find useful for me = sometimes) Instead of: 22596 cat STRU struct stat {dev=3D89, ino=3D3320836, = mode=3D-r--r--r-- , nlink=3D1, uid=3D0, gid=3D0, atime=3D1284725358, = stime=3D1284485510, ctime=3D1284485510, birthtime=3D1284485509, = size=3D1172220, blksize=3D16384, blocks=3D2336, flags=3D0x20000 } I get this now (including major and minor): 22596 cat STRU struct stat {dev=3D<id=3D89:M=3D0:m=3D89> = (/dev/ad4s1a), ino=3D3320836, mode=3D-r--r--r-- , nlink=3D1, uid=3D0, = gid=3D0, atime=3D1284725358, stime=3D1284485510, ctime=3D1284485510, = birthtime=3D1284485509, size=3D1172220, blksize=3D16384, blocks=3D2336, = flags=3D0x20000 } I wouldn't mind having someone help me whenever and if I get stuck on = the technical side (*wink* Alexander Leidinger *wink*) and also to give = me more insight on what the road to help in this should be. P.S.: I'm still going through "man style" hence no patch attached. If = anyone finds this one useful, I'll reply with the patch though.=20 -- Norberto=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?8C5C36F5-A070-4CBA-8B8C-6751F8D636E1>