Date: Fri, 26 Oct 2007 05:34:56 +1000 From: Peter Jeremy <peterjeremy@optushome.com.au> To: freebsd-stable@freebsd.org Subject: kdump(1) differences between 6.x and 7.x Message-ID: <20071025193456.GG70883@server.vk2pj.dyndns.org>
next in thread | raw e-mail | index | archive | help
--9crTWz/Z+Zyzu20v Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable In May 2006, netchild@ committed some changes to kdump to enhance the decoding of various syscall arguments. Using the example from the commit message: Change kdump to print more useful information, i.e. it changes from 32229 telnet CALL mmap(0,0x8000,0x3,0x1002,0xffffffff,0,0,0) 32229 telnet CALL open(0x2807bc28,0,0x1b6) 32229 telnet CALL socket(0x2,0x2,0) to 32229 telnet CALL mmap(0,0x8000,PROT_READ|PROT_WRITE,MAP_PRIVATE|MAP_ANO= N,0xffffffff,0,0,0) 32229 telnet CALL open(0x2807bc28,O_RDONLY,<unused>0x1b6) 32229 telnet CALL socket(PF_INET,SOCK_DGRAM,0) Would this change be eligible for an MFC to 6.x? It makes reading kdump output much easier. The only downside is that it might break scripts that people might use to postprocess kdump output. --=20 Peter Jeremy --9crTWz/Z+Zyzu20v Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.4 (FreeBSD) iD8DBQFHIO/g/opHv/APuIcRAvAcAJ9SGT9K/wCaFzeV97ieOdHNGpJx/ACeJ2nh J2cHSUBETZiQX68SAMXb86Y= =wmyK -----END PGP SIGNATURE----- --9crTWz/Z+Zyzu20v--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20071025193456.GG70883>