[Bug 1830796] Re: [Bionic][ARM64]Failure debugging linux kernel

Brian Murray brian at ubuntu.com
Fri Jun 28 16:04:36 UTC 2019


Actually the version number used in the debdiff (8.1-0ubuntu4) had
already been uploaded to the archive and so it was rejected. This is
part of why
https://wiki.ubuntu.com/SecurityTeam/UpdatePreparation#Update_the_packaging
recommends appending a .1 to the package version number, which is what I
did.

-- 
You received this bug notification because you are a member of Ubuntu
Sponsors Team, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/1830796

Title:
  [Bionic][ARM64]Failure debugging linux kernel

Status in gdb package in Ubuntu:
  Fix Released
Status in gdb source package in Bionic:
  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 could be to architectures other than ARM64 due to changes to gdb/util.c. Please see comment #2 where I have tested the PPA package on a ppc64el system and found it does not introduce any regressions.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gdb/+bug/1830796/+subscriptions



More information about the Ubuntu-sponsors mailing list