Alain Kalker [2009-11-28 11:27 -0000]: > This does raise another question: why do you use a package's > Dependencies and not the actual libraries from ProcMaps (including that > is a very smart move BTW :-) ) to decide which -dbgsym packages to > install?
It's actually doing both: It first installs all the packages in Dependencies:, and then trawls through ProcMaps to grab some more on a best-effort basis. Dependencies is preferred because it contains the version numbers of the library packages, so that we know why a retrace failed. ProcMaps.txt doesn't provide that. > For crash analysis it is not that important which packages a package > _claims_ to Depend on, it matters which libraries were _actually in its > address space_ when it crashed. Right, but due to the way the shlibs system works in Debian/Ubuntu, library dependencies are very reliable. > For example, an application might have pulled in a library from another > package during dynamic linking These are included in Dependencies: (it's the full transitive dependency tree). > , or it might have dlopen'ed a plugin library Those are collected from ProcMaps parsing indeed. -- apport doesn't include Package in report when invoked on core dump https://bugs.launchpad.net/bugs/487759 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
