[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.
[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] debug/boot/ vmlinux- 4.18.0- 20-generic /proc/kcore /boot/vmlinuz- 4.18.0- 20-generic root=UUID= edb5e5a7- 8272-4e13- aa25-37' .
# gdb /usr/lib/
[New process 1]
Core was generated by `BOOT_IMAGE=
#0 0x0000000000000000 in ?? ()
(gdb) p jiffies_64
Cannot access memory at address 0xffff000009616980
(gdb)
[Fix] sourceware. org/git/ binutils- gdb.git) by the following patch:
This issue was fixed upstream (git://
8727de56b0 Fix tagged pointer support
[Regression Potential]
The risk of regression after applying this patch is low, tagged pointer test cases still pass.