Aurelien Jarno wrote: >> the debug package doesn't help anyhow when inspecting core dumps. It would >> be much useful if the package would provide the symbols for local >> variables and thelike to get the full backtrace with gdb. That's also >> what other debug packages of libraries do. > > The drawback of providing all symbols is that it makes gdb very slow to > load all symbols, render it almost unusable.
Perhaps, the symbol file can be put in a non-standard location so that gdb does not load it by default. And if it is really needed, the admin just has to move or create a symlink to the file (or to load it explicitly in gdb if it is possible)... >> Quoting the discussion on #513341: >> >> Daniel Jacobowitz hat am Thu 05. Feb, 14:03 (-0500) geschrieben: >>> On Mon, Feb 02, 2009 at 10:12:37PM +0100, Jörg Sommer wrote: >>>> But this doesn't work for core dumps. I would like to get more >>>> informations, like local variables from core dumps. How can I get such >>>> informations with the debugging library in /usr/lib/debug? >>> Sorry, there's no way to do this with the current packages. > -- Vincent Danjean GPG key ID 0x9D025E87 [email protected] GPG key fingerprint: FC95 08A6 854D DB48 4B9A 8A94 0BF7 7867 9D02 5E87 Unofficial pacakges: http://www-id.imag.fr/~danjean/deb.html#package APT repo: deb http://perso.debian.org/~vdanjean/debian unstable main -- To UNSUBSCRIBE, email to [email protected] with a subject of "unsubscribe". Trouble? Contact [email protected]
