Darren J Moffat wrote:
> Bart Smaalders wrote:
>> John Levon wrote:
>>> Has someone thought through the implications of the IPS approach on
>>> the CTF parts of the kernel build? (See
>>> http://blogs.sun.com/levon/entry/reducing_ctf_overhead if you need
>>> context)
>>
>> From the referenced blog:
>>
>>> For the sake of kmdb and crash dumps, the CTF data for each kernel
>>> binary is present in the memory image of a booted kernel.
>>
>> Since the ctf data is present in the in memory portion of the elf files,
>> it is part of the elf hash and thus any file w/ varying cft data
>> should be
>> part of the new package(s).
>
> I don't know much about CTF but why is it in the in memory portion of
> the ELF file ? Is this so that DTrace and mdb can depend on it being
> loaded ?
>
1: Dtrace & mdb
2: What the blog says: "For the sake of kmdb and crash dumps, the CTF
data for each kernel binary is present in the memory image of a booted
kernel." If you boot a kernel, patch current loaded binaries on
disk and
then panic, the core dump will contain the correct information.
- Bart
--
Bart Smaalders Solaris Kernel Performance
[EMAIL PROTECTED] http://blogs.sun.com/barts
"You will contribute more with mercurial than with thunderbird."
_______________________________________________
pkg-discuss mailing list
[email protected]
http://mail.opensolaris.org/mailman/listinfo/pkg-discuss
