kdump(1) differences between 6.x and 7.x

[Peter Jeremy]

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_ANON,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.

-- 
Peter Jeremy
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 187 bytes
Desc: not available
Url : http://lists.freebsd.org/pipermail/freebsd-stable/attachments/20071026/84cd7e62/attachment.pgp