On Tue, Jan 18, 2022 at 01:47:04PM -0500, Dan Streetman wrote: > On Fri, Jan 7, 2022 at 5:10 PM Bryce Harrington > <[email protected]> wrote: > > On Fri, Jan 07, 2022 at 08:34:57PM +0530, Utkarsh Gupta wrote: > > > Here's an update: we couldn't find anything worthwhile from the > > > upstream tracker or changelog or anything and neither of us have > > > enough experience with crash files. > > > > Here's a paint-by-numbers way to get stacktraces from .crash files:
I've taken this writeup and reformatted it for the UMH, here's a PR: https://github.com/canonical/ubuntu-maintainers-handbook/pull/38 > > 0. Enable debug symbols. Various ways to do this, one way is to append > > ddebs to your apt sources: > > > > $ echo "deb http://ddebs.ubuntu.com focal main restricted universe > > multiverse" | sudo tee -a /etc/apt/sources.list > > $ echo "deb http://ddebs.ubuntu.com focal-updates main restricted > > universe multiverse" | sudo tee -a /etc/apt/sources.list > > > > $ sudo apt install ubuntu-dbgsym-keyring > > $ sudo apt update > > > > 1. Install package with debug symbols > > > > $ sudo apt install bind9 bind9*-dbgsym > > Note this (using ddebs repo) only works if the crash resulted with the > latest version of all associated packages; in a normal support > situation where at least some package versions (that are relevant to > what caused the crash, e.g. application package and dep libs) are not > the latest, the ddebs repo unfortunately isn't useful since it only > provides the dbgsyms for the latest package versions. Yep, that's certainly right. Like I mentioned in step 0 there are for sure a variety of ways to do this, this should be taken as just one of multiple examples. When I was maintaining X.org we unfortunately could not rely on -dbgsym packages as ddebs weren't available for video drivers, and users had to use a different approach to get debug symbols. You describe another common use case. I imagine there's many more... > It's frequently more helpful to simply use pull-lp-ddebs to get the > specific dbgsyms for the package versions that generated the crash > file. Interesting, this is the first I've heard of pull-lp-ddebs, but that definitely sounds quite relevant to this. > Of course, hopefully eventually someone (*ahem* sergiodj) will get an > Ubuntu debuginfod server set up, which would allow direct access to > the appropriate dbgsyms, but that's not available yet. Agreed. Let's use the PR as a starting point for accumulating more tips and advice: https://github.com/canonical/ubuntu-maintainers-handbook/pull/38 Thanks everyone who's provided feedback so far. Please provide copyedits to the above so we can capture the best advice. Bryce -- ubuntu-server mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-server More info: https://wiki.ubuntu.com/ServerTeam
