Alexander Kolbasov wrote:
> Ali Bahrami <[EMAIL PROTECTED]> wrote:
>
> Ali> I'm betting that these are local symbols referenced by the
> .SUNW_ldynsym
> Ali> section, which is an allocable section, and therefore uses the
> Ali> dynstr:
>
> Are these randomly generated during each build or they are
> deterministic? Does it mean that wsdiff will always pick these up as a
> change in libc?
>
> - Akolb
Unless I'm missing something (certainly possible), Adam already covered
the answers to both questions.
> dtrace -G chooses a randomly generated prefix for the symbols. They should
> change every time a workspace is built.
This accounts for the fact that the names change.
My bit was to explain why those names are showing up in the dynstr
at all --- because we have a "local dynamic" symbol table, and
those local function symbols are ending up in it. The linker is doing
what it ought to do in this situation.
And, the symbols will disappear once
6602451 new symbol visibilities required: EXPORTED, SINGLETON and
ELIMINATE
gets integrated, and then 'dtrace -G' gets modified to use
the ELIMINATE feature. So wsdiff will be picking up these as changes
in libc until those two things happen.
- Ali
_______________________________________________
dtrace-discuss mailing list
[email protected]
