Op zaterdag 28-11-2009 om 12:27 uur [tijdzone +0100], schreef Alain Kalker: > 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?
May I propose another (complementary) workflow? - On the machine doing the retracing, use apt-file (package: apt-file) to gather a list of all files in all packages available in the active repositories on the crash machine. - For the executable and all libraries listed in ProcMaps, do an `apt-file search` to get the packages to which these libraries belong. - Get the corresponding -dbgsym packages. - If any library listed in ProcMaps doesn't show up in `apt-file search`, trigger an update (`apt-file update`), and repeat the search once more. - If still no match, we're SOL (assume the library is proprietary/unsupported and be done with it). - Finally, do the retrace. I do realize that this doesn't replace the current workflow (for interpreted languages you will still need another dependency resolver), but it can greatly enhance it. Kind regards, Alain -- 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
