On Fri, 2024 May 31 18:36-04:00, Andres Salomon wrote: > > I'm going from memory here, but I believe the dak installation on > security.debian.org doesn't keep dbgsym packages for historical reasons. > Thus, they're only available once chromium gets moved to > stable-proposed-updates. https://tracker.debian.org/pkg/chromium shows > .60 as being the last one in stable-p-u. At some point in the next week > or two, someone from the release team will likely accept the newer > chromium packages into stable-p-u, at which point the dbgsym packages > for .141 (or whatever the latest version is) will be available.
Eeegh, not a great state of affairs for a package that revs this often. > It sucks, but it is what it is. You could either spend a bunch of time > building chromium for the dbgsym packages, or I could put my local build > of .141 online w/ dbgsym packages for you to try out (assuming amd64?), > or you could downgrade to .60 and use those dbgsym packages. If it's not too much trouble to put up that .141 package (and the problem still persists in that version), I'll gladly make use of it. > Yes, just running 'chromium -g' will launch it inside gdb; you may have > to manually type 'run' to start it inside gdb, I forget. But then > you'll get a backtrace (or you can ctrl-c and run 'bt', if it's a > deadlock or something). I haven't bothered w/ core dumps of chromium > before, so I can't speak to that. Understood. The system in question is a bit tight on memory, so hopefully it won't fall over with Chromium under GDB. --Daniel
