Darren J Moffat wrote:
> Milan Jurik wrote:
>> I could hack it to the module by some Makefile, but it will change
>> revision in every build, not good for new packaging system I think.
>
> It seems to me that the simplest solution here is to have at least the
> .SUNW_signature section in a kernel crash dump and in a userland core
> file. That means no new build process and it works for all
> consolidations that have their binaries signed and any 3rd party code
> that is also signed. See 6365439 which I logged on 2005-12-20.
>
It seems to me that there is still a gap between identifying
binaries and determining the underlying source files?
As far as I know we can get the filenames from the nametable with nm
and we can get the complete source if someone opts to compile in
complete debugging (with the associated bloat.) To me, being able to
get an MD5/SHA1/etc hash for each source file and having a fingerprint
database for (open)solaris source files seems to be the gap the %I% was
improperly filling.
-Will
