I was using the following version of gdb in both chroots: GNU gdb (Ubuntu 7.11.90.20161005-0ubuntu1) 7.11.90.20161005-git
-- 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/1645501 Title: corefiles not created in armhf chroot on arm64 porter Status in gdb package in Ubuntu: New Bug description: 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://code.launchpad.net/~daisy-pluckers/error-tracker-deployment /test-crashes) crash files produced for armhf are crash files without CoreDumps. This happened sometime between 20160531 and 20161025. I've recreated this on the porter-arm64 box with the following minimal test case (generate-sigsegv-crash.py is from apport-test-crashes): schroot -c yakkety-armhf python generate-sigsegv-crash.py cat 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/unix/syscall-template.S:84 49 84 ../sysdeps/unix/syscall-template.S: No such file or directory. 50 (gdb) Saved corefile /tmp/tmp840s08i1/my.core armhf chroot on porter-arm64: 47 Program received signal SIGSEGV, Segmentation fault. 48 0xf772f9e4 in read () at ../sysdeps/unix/syscall-template.S:84 49 84 ../sysdeps/unix/syscall-template.S: No such file or directory. 50 (gdb) Unable to fetch the floating point registers.: Invalid argument. Notice how there is no core file save on porter-arm64. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdb/+bug/1645501/+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
