The apport workaround is ugly in two ways: First it is a workaround and
second it needs root permission:
```
Traceback (most recent call last):
File "/home/ubuntu/apport/bin/apport-retrace", line 688, in
main()
File "/home/ubuntu/apport/bin/apport-retrace", line 441, in main
os.mkdir(
This bug was fixed in the package apport - 2.20.11-0ubuntu75
---
apport (2.20.11-0ubuntu75) jammy; urgency=medium
* bin/apport-retrace: For releases which gdb doesn't search in the
debug-file-directory for .gnu_debugaltlink create a symlink from the
host's .dwz to the machin
** Branch linked: lp:~ubuntu-core-dev/ubuntu/jammy/apport/ubuntu
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1818918
Title:
gdb doesn't search in debug-file-directory for .gnu_debugaltlink
To man
Ah, good to know! No problem at all, Brian! Cheers :-)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1818918
Title:
gdb doesn't search in debug-file-directory for .gnu_debugaltlink
To manage noti
@Sergio - Given the way the retracers are currently setup we are using
the version of gdb for the release for the crash we are retracing,
subsequently we'd need to SRU this to every release. Given that I've
already worked around this specific issue in apport backporting the fix
seems unnecessary.
gdb (10.1-1.3) unstable; urgency=medium
* Non-maintainer upload.
* Convert to debhelper v10, not using the sequencer. Addresses: #973355.
* Search for DWZ files in debug-file-directories as well, patch taken
from the trunk.
* Only build with debuginfod on linux targets.
-- Matthias K
Ah, I see that is has indeed been backport by Debian, and is already in
hirsute: debian/patches/2bf3b79d05bf85e41cbdcb020bd1cc424f59dd9a.diff is
the patch. @Brian, would you like me to backport the patch to another
release?
--
You received this bug notification because you are a member of Ubuntu
@Brian, Ops, sorry. I forgot about this bug, and then I kind of assumed
that it had already been backported on Debian. This is just for
hirsute, right? I can backport it now, give me just a second.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscrib
@Sergio - Is this still something you are planning on backporting?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1818918
Title:
gdb doesn't search in debug-file-directory for .gnu_debugaltlink
To m
FWIW, the fix has just been pushed upstream:
https://sourceware.org/git/?p=binutils-
gdb.git;a=commit;h=2bf3b79d05bf85e41cbdcb020bd1cc424f59dd9a
If no one else beats me to it, I can try to backport it this weekend.
--
You received this bug notification because you are a member of Ubuntu
Bugs, w
@sergiodj many thanks for the help here
It was a dwz man page somewhere that made me think we might be misusing
.gnu_debugaltlink somehow (didn't even know about dh_dwz), but on a
quick search I couldn't understand how the path was supposed to look
like so I could test that idea with my replace-al
@tdaitx asked me to take a look at this problem, and here is what I
found.
1) As he said above, the problem is that Debian/Ubuntu generate
.gnu_debugaltlink sections containing full pathnames to the DWZ alt
debug files. IMO, we should be using dwz's "--relative" option when
invoking it via dh_dwz
So the issue is: if there is a .gnu_debugaltlink GDB will try to load
that file and throw an error if it can't. That path is absolute and GDB
does _not_ look for that path/file anywhere else, not even inside
'debug-file-directory'.
GDB seems to only look at section .gnu_debugaltlink in debug/.buil
I was able to reproduce what Brian is reporting here.
If the -dbgsym for the package is installed, gdb works and reports that it is
reading from the /tmp/dbgsym path. When -dbgsym package is not installed then
it fails with the
'could not find '.gnu_debugaltlink' file for ...' message
--
You
This is still an issue with hirsute afaict.
(hirsute-amd64)root@impulse:/tmp# gdb --ex 'set debug-file-directory
/tmp/dbgsym/usr/lib/debug:/usr/lib/debug' --ex 'file /bin/cat' --ex 'cor
e-file /tmp/cat.core'
GNU gdb (Ubuntu 10.1-0ubuntu1) 10.1
Copyright (C) 2020 Free Software Foundation, Inc.
Lic
I tried the testcase from comment #12 in Focal and Hirsute and it worked
just fine:
$ gdb --ex 'set debug-file-directory /tmp/dbgsym/usr/lib/debug:/usr/lib/debug'
--ex 'file /bin/cat' --ex 'core-file /tmp/cat.core'
Type "apropos word" to search for commands related to "word".
Reading symbols from
Ah, thanks for pointing that out but there is still an issue with the
test case in comment #12 as the .gnu_debugaltlink file is still not
loaded.
Reading symbols from /bin/cat...
Reading symbols from
/tmp/dbgsym/usr/lib/debug/.build-id/fb/a7cee6aca864b8f79dfaa8a267855333b445c1.debug...
could not
> 7) Execute "gdb --ex 'file /bin/cat' --ex 'core-file /tmp/cat.core'
--ex 'set debug-file-directory /tmp/dbgsym/usr/lib/debug'"
Try setting the debug-file-directory first, it should work.
gdb --ex 'set debug-file-directory /tmp/dbgsym/usr/lib/debug:/usr/lib/debug'
--ex 'file /bin/cat' --ex 'core
This is also true with gdb 10.1 from hirsute-proposed.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1818918
Title:
gdb doesn't search in debug-file-directory for .gnu_debugaltlink
To manage notifi
I've come up with a simpler test case on an Ubuntu 20.10 system which
follows:
1) Execute 'gdb --args cat'
2) in gdb type 'run'
3) press Ctrl-Z
4) in gdb type 'generate-core-file /tmp/cat.core'
5) download the dbgsym for coreutils
6) Extract them 'dbg-deb -x coreutils-dbgsym_8.32-3ubuntu1_amd64.dd
Oh and using either of '/tmp/dbgsym' or /tmp/dbgsym/usr/lib/debug' for
the debug-file-directory works.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1818918
Title:
gdb doesn't search in debug-file-d
Here's the full strace for the /bin/cat test case.
** Attachment added: "gdb-bin-cat.trace"
https://bugs.launchpad.net/ubuntu/+source/gdb/+bug/1818918/+attachment/5431989/+files/gdb-bin-cat.trace
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscrib
** Changed in: apport
Status: In Progress => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1818918
Title:
gdb doesn't search in debug-file-directory for .gnu_debugaltlink
To man
** Branch linked: lp:apport
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1818918
Title:
gdb doesn't search in debug-file-directory for .gnu_debugaltlink
To manage notifications about this bug go t
I've managed to workaround this in apport by creating a symlink from the
host system's /usr/share/debug/.dwz to the gdb sandbox's
/usr/share/debug/.dwz folder. That being said I still think there is an
issue with gdb not checking the debug-file-directory for the "Separate
debug info file" in the .g
** Tags added: fr-823
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1818918
Title:
gdb doesn't search in debug-file-directory for .gnu_debugaltlink
To manage notifications about this bug go to:
htt
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: gdb (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1818918
Title:
gdb do
** Changed in: gdb (Ubuntu)
Status: Expired => New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1818918
Title:
gdb doesn't search in debug-file-directory for .gnu_debugaltlink
To manage not
[Expired for gdb (Ubuntu) because there has been no activity for 60
days.]
** Changed in: gdb (Ubuntu)
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1818918
Title
I've discovered that I can workaround this issue by modifying the
argument passed to the 'set debug-file-directory' option of gdb e.g. by
using the following:
'set debug-file-directory /srv/vms/apport-sandbox-dir/Ubuntu 19.10/amd64
/report-sandbox/usr/lib/debug/.dwz/'
I no longer see the error me
looking up the .gnu_debugaltlink in a normal debug session works
perfectly fine. Please can you show this behavior without any sandbox,
or try to diagnose why it doesn't work in this sandbox? I am not
familiar with this sandbox environment.
** Changed in: gdb (Ubuntu)
Status: New => Inco
I recently started seeing issues with some other applications too e.g.:
Reading symbols from /srv/vms/apport-sandbox-dir/Ubuntu
19.10/amd64/report-sandbox//usr/lib/gdm3/gdm-session-worker...
Reading symbols from /srv/vms/apport-sandbox-dir/Ubuntu
19.10/amd64/report-sandbox/usr/lib/debug/.build-i
** Changed in: gdb (Ubuntu)
Status: Expired => New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1818918
Title:
gdb doesn't search in debug-file-directory for .gnu_debugaltlink
To manage not
[Expired for gdb (Ubuntu) because there has been no activity for 60
days.]
** Changed in: gdb (Ubuntu)
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1818918
Title
This test case doesn't involve snaps, notice the file switch to gdb:
--ex 'file "/srv/vms/apport-sandbox-dir/Ubuntu 19.04/amd64/report-
sandbox//usr/bin/gnome-calculator"'
This is still an issue with the version of gdb from eoan, 8.3-0ubuntu1,
and eoan's gnome-calculator package.
Calling gdb com
please can you can up with a test case not involving snaps? Asking
because I can't.
** Changed in: gdb (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1818918
This is still an issue with gdb version 8.2.90.20190311-0ubuntu1 in
disco.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1818918
Title:
gdb doesn't search in debug-file-directory for .gnu_debugaltli
** Attachment added: "strace of gdb"
https://bugs.launchpad.net/ubuntu/+source/gdb/+bug/1818918/+attachment/5244184/+files/strace-gdb.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1818918
Titl
38 matches
Mail list logo
