corefiles not created in armhf chroot on arm64 porter
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
gdb (Ubuntu) |
Fix Released
|
High
|
Brian Murray | ||
Precise |
Invalid
|
Medium
|
Unassigned | ||
Trusty |
Triaged
|
Medium
|
Brian Murray | ||
Xenial |
Triaged
|
Medium
|
Brian Murray | ||
Yakkety |
Fix Released
|
Medium
|
Brian Murray |
Bug Description
Impact
------
Its not possible to create a corefile in an armhf chroot on an arm64 system.
Test Case
---------
On an arm64 system enter an armhf chroot, then
1) execute "gdb --args cat"
2) in gdb type run
3) press Ctrl-Z
4) generate-core-file /tmp/my.core
With the current version of gdb you'll see "Unable to fetch floating point registers.", with the version in -proposed you'll see "Saved corefile".
Regression Potential
-------
The corefiles aren't created at all in this scenario so things should improve.
I'm filing this about gdb per Steve's suggestion, although this could be an issue somewhere else.
I recently discovered that the apport-test-crash (https:/
schroot -c yakkety-armhf
python generate-
Running this on both armhf and arm64 we can see the following different output.
armhf chroot on porter-armhf:
47 Program received signal SIGSEGV, Segmentation fault.
48 0xb6f599e4 in read () at ../sysdeps/
49 84 ../sysdeps/
50 (gdb) Saved corefile /tmp/tmp840s08i
armhf chroot on porter-arm64:
47 Program received signal SIGSEGV, Segmentation fault.
48 0xf772f9e4 in read () at ../sysdeps/
49 84 ../sysdeps/
50 (gdb) Unable to fetch the floating point registers.: Invalid argument.
Notice how there is no core file save on porter-arm64.
tags: | added: patch |
Changed in gdb (Ubuntu): | |
assignee: | nobody → Brian Murray (brian-murray) |
Changed in gdb (Ubuntu Precise): | |
status: | New → Triaged |
Changed in gdb (Ubuntu Trusty): | |
status: | New → Triaged |
Changed in gdb (Ubuntu Xenial): | |
status: | New → Triaged |
Changed in gdb (Ubuntu Yakkety): | |
status: | New → Triaged |
description: | updated |
Changed in gdb (Ubuntu Yakkety): | |
assignee: | nobody → Brian Murray (brian-murray) |
importance: | Undecided → Medium |
Changed in gdb (Ubuntu Xenial): | |
importance: | Undecided → Medium |
Changed in gdb (Ubuntu Trusty): | |
importance: | Undecided → Medium |
Changed in gdb (Ubuntu Precise): | |
importance: | Undecided → Medium |
Changed in gdb (Ubuntu Precise): | |
status: | Triaged → Invalid |
I was using the following version of gdb in both chroots:
GNU gdb (Ubuntu 7.11.90. 20161005- 0ubuntu1) 7.11.90. 20161005- git