> From: Bart Smaalders <[EMAIL PROTECTED]>
> 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).
>
> There are distinct implications of CTF on the number of binaries changed
> in each build; this will need to be explored.
>
> If necessary, we may need to work on making the CTF construction
> process more deterministic.
While the .SUNW_ctf section is of type SHT_PROGBITS, the flags on this
section don't include SHF_ALLOC. Hence this section doesn't appear in
the process address space and is not part of of the elfsign hash for
non-crypto objects. The elfsign hash for crypto objects, which number
approximately two dozen, does include this section.
-JZ
_______________________________________________
pkg-discuss mailing list
[email protected]
http://mail.opensolaris.org/mailman/listinfo/pkg-discuss
