Package: gdb Severity: wishlist Hi,
I’ve been pondering for a while a way to improve the automated tracing of crashes using debugging symbols available remotely, and I’m stuck in my reflexions because of a problem in gdb. When you install a libfoo-dbg package which has split debugging symbols, and you debug a program using libfoo, gdb looks for the libfoo symbols in /usr/lib/debug, and that works very nicely. However, I noticed that gdb reads the whole split symbols file, and the reason is that it computes its CRC32 checksum and compares it to the one in the library’s header. Because of that, it is not possible to access directly to the debugging symbols over the network; it would require a huge network traffic, just as important as downloading the whole debugging packages. 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. At the very least, would you accept a patch that disables the CRC32 check using a command-line option? 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
