Bug#518134: gdb: please don't read the whole file when using split symbols

2009-03-04 Thread Daniel Jacobowitz
On Wed, Mar 04, 2009 at 04:35:29PM +0100, Josselin Mouette wrote: > 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? IMO yes. > This would be nice. Also, looking at the documenta

Bug#518134: gdb: please don't read the whole file when using split symbols

2009-03-04 Thread Josselin Mouette
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; othe

Bug#518134: gdb: please don't read the whole file when using split symbols

2009-03-04 Thread Daniel Jacobowitz
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 disc

Bug#518134: gdb: please don't read the whole file when using split symbols

2009-03-04 Thread Josselin Mouette
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, a