Le mercredi 04 mars 2009 à 10:12 -0500, Daniel Jacobowitz a écrit : > On Wed, Mar 04, 2009 at 11:49:48AM +0100, Josselin Mouette wrote: > > Therefore, it would be very nice to think of a way to not make this > > reading happen. I don’t think it is necessary to check the whole file’s > > CRC32; other mechanisms (like dependencies) should prevent the files > > from having discrepancies. Just to be safe, you could store a generated > > UUID in both file headers, and that would not require reading the whole > > files. > > This is possible using build-id notes. However, I don't know what > changes across the distribution would be required for that. We'd have > to generate them for all binaries and libraries if we aren't already.
I guess it means changing the default for ld, which is currently set to not generating them by default, AFAICT. Should I report another bug against binutils, then? > After that, if GDB locates a debug file by using build ID it won't > check the crc. I think it will still check CRC's if it searches > /usr/lib/debug, but that could be fixed in a very straightforward manner. This would be nice. Also, looking at the documentation, it would be a very elegant way to store the debugging symbols for many versions in a single online directory structure. There wouldn’t be a need to create a virtual filesystem layout pointing to the correct debugging symbols since the build IDs are unique. Thanks, -- .''`. Debian 5.0 "Lenny" has been released! : :' : `. `' Last night, Darth Vader came down from planet Vulcan and told `- me that if you don't install Lenny, he'd melt your brain.
signature.asc
Description: Ceci est une partie de message numériquement signée
