gdb sandbox creation should use report's libc6 version
Bug #1819230 reported by
Brian Murray
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Apport |
Triaged
|
Medium
|
Unassigned | ||
Bug Description
When the gdb sandbox is created for retracing a crash we also install the dependencies of gdb which includes libc6. This can cause issues because we install the latest version of libc6 as a dependency and if the report has an older version of libc6 this can at best cause a version mismatch when running gdb or cause gdb to hang as seen in bug 1760207.
It'd be better if apport were to check the version of libc6 used in the report and then tried to install that specific version of libc6 in the gdb sandbox instead of just installing the latest version of libc6.
Revision history for this message
| Brian Murray (brian-murray) wrote | #1 |
| Changed in apport: | |
| importance: | Undecided → Medium |
| status: | New → Triaged |
To post a comment you must log in.
I've currently worked around this issue, which is more common when retracing crashes from the development release of Ubuntu, by disabling -proposed in the sources.list file for the retracers. The logic being that people shouldn't be using -proposed from the development release anyway as the packages have not migrated possibly due to failures in automatic testing.