Idea from sprint discussion: In apport: - Don't try to run gdb from the retracing target sandbox
- Add --gdb-root <path> argument to apport-retrace that will set PATH, LD_LIBRARY_PATH, and possibly some env var to specify the gdb plugin dir to appropriate subdirs of <path>. Calling "gdb" should then prefer running gdb from that dir. In the retracer deployment: - add --gdb-root on the sandbox with the same release but the host's native architecture - Ensure that gdb is installed in that -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apport in Ubuntu. https://bugs.launchpad.net/bugs/1517257 Title: apport-retrace should install and use gdb for target release Status in Apport: Triaged Status in apport package in Ubuntu: Triaged Bug description: apport-retrace will use the version of gdb installed on the system performing the retrace. This can cause issues retracing crash reports from releases that have a newer toolchain revision than the system performing the retrace. Subsequently, it would be better if apport- retrace were to install gdb into the sandbox being used for retracing and used that version of gdb for analyzing the core dump. To manage notifications about this bug go to: https://bugs.launchpad.net/apport/+bug/1517257/+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
