The attached debdiff to gdb fixes the issue. The patch was cleanly applied from the upstream GDB git repo, and test results are as posted to this bug report. No regression were found.
** Patch added: "Fix tagged pointer support." https://bugs.launchpad.net/ubuntu/+source/gdb/+bug/1830796/+attachment/5267248/+files/gdb-fix-tagged-pointer-support.diff -- 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/1830796 Title: [Bionic][ARM64]Failure debugging linux kernel Status in gdb package in Ubuntu: In Progress Bug description: [Impact] GDB fails to debug ARM64 vmlinux debug image with proc/kcore information. For example it is unable to print values of variables like 'jiffies_64'. [Test] # gdb /usr/lib/debug/boot/vmlinux-4.18.0-20-generic /proc/kcore [New process 1] Core was generated by `BOOT_IMAGE=/boot/vmlinuz-4.18.0-20-generic root=UUID=edb5e5a7-8272-4e13-aa25-37'. #0 0x0000000000000000 in ?? () (gdb) p jiffies_64 Cannot access memory at address 0xffff000009616980 (gdb) [Fix] This issue was fixed upstream (git://sourceware.org/git/binutils-gdb.git) by the following patch: 8727de56b0 Fix tagged pointer support [Regression Potential] The risk of regression after applying this patch is low, tagged pointer test cases still pass. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdb/+bug/1830796/+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