Subject: Re: kdump dependency on kernel, ktrace id portability
To: Emmanuel Dreyfus <manu@NetBSD.org>
From: Nathan J. Williams <email@example.com>
Date: 12/29/2003 14:06:13
manu@NetBSD.org (Emmanuel Dreyfus) writes:
> Second idea: create a new EMUL record (with a different id), which would
> provide the emulation name with the system call table. This would grow a
> bit the ktrace.out files, but they would be readable anywhere.
Do I understand correctly that you want the ktrace facility to write
the table of syscall names to the ktrace.out file? How big is that
table? I'm more concerned with the space it occupies in the kernel
than the space it occupies in the ktrace.out file.
I have to admit that I see this as adding stuff to the kernel to solve
a pretty minor problem that only happens to developers active in a