Public bug reported: apport-retrace utilizes gdb in a sandbox and sets multiple configuration options so that is possible to retrace crashes from an operating system other than that in which the crash occurred. This was working great until gdb version 8.2.50.20190213-0ubuntu1 became available for disco. Here's an example of the gdb command used:
Calling gdb command: '/srv/vms/apport-sandbox-dir/Ubuntu 19.04/amd64 /report-sandbox/lib/x86_64-linux-gnu/ld-linux-x86-64.so.2' '/srv/vms /apport-sandbox-dir/Ubuntu 19.04/amd64/report-sandbox/usr/bin/gdb' --ex 'set debug-file-directory /srv/vms/apport-sandbox-dir/Ubuntu 19.04/amd64 /report-sandbox/usr/lib/debug' --ex 'set solib-absolute-prefix /srv/vms /apport-sandbox-dir/Ubuntu 19.04/amd64/report-sandbox' --ex 'add-auto- load-safe-path /srv/vms/apport-sandbox-dir/Ubuntu 19.04/amd64/report- sandbox' --ex 'set solib-search-path /srv/vms/apport-sandbox-dir/Ubuntu 19.04/amd64/report-sandbox/lib/x86_64-linux-gnu' --ex 'set data- directory /srv/vms/apport-sandbox-dir/Ubuntu 19.04/amd64/report- sandbox/usr/share/gdb' --ex 'file "/srv/vms/apport-sandbox-dir/Ubuntu 19.04/amd64/report-sandbox//usr/bin/gnome-calculator"' --ex 'core-file /tmp/apport_core_hj0ttq6p' With the new versions of gdb multiple shared object libraries are no longer loaded when analyzing the same crash file. I'll add the differences as comments. ** Affects: gdb (Ubuntu) Importance: Undecided Status: New ** Tags: disco regression-release -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gdb in Ubuntu. https://bugs.launchpad.net/bugs/1818884 Title: gdb versions greater than 8.2.50 don't always respect solib-search- path Status in gdb package in Ubuntu: New Bug description: apport-retrace utilizes gdb in a sandbox and sets multiple configuration options so that is possible to retrace crashes from an operating system other than that in which the crash occurred. This was working great until gdb version 8.2.50.20190213-0ubuntu1 became available for disco. Here's an example of the gdb command used: Calling gdb command: '/srv/vms/apport-sandbox-dir/Ubuntu 19.04/amd64 /report-sandbox/lib/x86_64-linux-gnu/ld-linux-x86-64.so.2' '/srv/vms /apport-sandbox-dir/Ubuntu 19.04/amd64/report-sandbox/usr/bin/gdb' --ex 'set debug-file-directory /srv/vms/apport-sandbox-dir/Ubuntu 19.04/amd64/report-sandbox/usr/lib/debug' --ex 'set solib-absolute- prefix /srv/vms/apport-sandbox-dir/Ubuntu 19.04/amd64/report-sandbox' --ex 'add-auto-load-safe-path /srv/vms/apport-sandbox-dir/Ubuntu 19.04/amd64/report-sandbox' --ex 'set solib-search-path /srv/vms /apport-sandbox-dir/Ubuntu 19.04/amd64/report-sandbox/lib/x86_64 -linux-gnu' --ex 'set data-directory /srv/vms/apport-sandbox- dir/Ubuntu 19.04/amd64/report-sandbox/usr/share/gdb' --ex 'file "/srv/vms/apport-sandbox-dir/Ubuntu 19.04/amd64/report- sandbox//usr/bin/gnome-calculator"' --ex 'core-file /tmp/apport_core_hj0ttq6p' With the new versions of gdb multiple shared object libraries are no longer loaded when analyzing the same crash file. I'll add the differences as comments. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdb/+bug/1818884/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp