Hi all

I was thinking about adding information about mach trap processing in
ktrace. Today we have this:
  1413 ls       CALL  msg_trap(0xffffd970,0x3,0x18)
  1413 ls       RET   msg_trap 0
  1413 ls       CALL  msg_trap(0xffffd970,0x3,0x24)
  1413 ls       RET   msg_trap 0

We could have this:
  1413 ls       CALL  msg_trap(0xffffd970,0x3,0x18)
  1413 ls       MACH  host_info(0xfffffda90)
  1413 ls       RET   host_info 0
  1413 ls       RET   msg_trap 0
  1413 ls       CALL  msg_trap(0xffffd970,0x3,0x24)
  1413 ls       MACH  vm_allocate(0x8000, 0x4000)
  1413 ls       RET   vm_allocate 0
  1413 ls       RET   msg_trap 0

This would help a lot when debugging mach traps (we could remove a huge
number of debug printf that mess the terminal and slow down the
execution). Does it seems a good idea or not (If it's not too disgusting
for most people, I'll start working on it)

--=20
Emmanuel Dreyfus.
Windows 95, Windows 98, Windows 2000, Windows Millenium
D=E9sormais, les OS portent la date de peremption dans leurs noms.
manu@netbsd.org