Add some more information in the ktrace(1)/kdump(1) output

Julian Elischer julian at
Wed Apr 19 21:14:53 UTC 2006

David Kirchner wrote:

>Please Cc: me on replies as I am not a member of this list.
>I'm working with Alexander Leidinger <netchild at> on the
>ktrace project mentioned on the ideas page. I've attached a patch,
>made against 6.1-RC (and should work against -CURRENT). The patch
>modifies kdump output to use strings instead of numbers for every(I
>believe) relevant syscall.
>For example, the output before:
> 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)
>is now:
> 32229 telnet   CALL 
> 32229 telnet   CALL  open(0x2807bc28,O_RDONLY,<unused>0x1b6)
> 32229 telnet   CALL  socket(PF_INET,SOCK_DGRAM,0)
>I'd appreciate any feedback you may have. This is just one half of the
>project; the other half will involve updating the kernel to include
>more data in the dump output. I'm thinking, specifically, adding
>KTR_STAT for stat() results and KTR_SOCKADDR for connect(), bind()
>arguments, and accept() results.
bind/connect would be particularly nice  ;-)

don't forget linux_kdump :-)

More information about the freebsd-arch mailing list