[Bug 1848200] autopkgtest failure investigation

dann frazier dann.frazier at canonical.com
Wed Nov 6 19:44:46 UTC 2019


Stable Release Team,

I investigated the autopkgtest regression in Comment #12, and believe
it to not be a regression introduced by this gdb upload. apport has
been updated a couple of times via security since tests passed - and at
least one of those updates had known regressions. There is also a
false positive result due to an aspell SRU (see bug
1851542). Apparently autopkgtests don't run on security uploads by
default, so autopkgtest.ubuntu.com doesn't have apples/apples test
results to compare (prev-gdb/prev-apport vs. prev-gdb/new-apport). I
therefore ran some tests manually.

In the attached logs you'll see that:
 - I am able to reproduce the same failures as the official
   autopkgtests for apport
 - The failures are the same with both the current gdb and the
   bionic-proposed gdb

Therefore, please allow gdb to promulgate to -updates.

 -dann


** Attachment added: "gdb.i386"
   https://bugs.launchpad.net/bugs/1848200/+attachment/5303314/+files/gdb.i386

** Attachment added: "gdb.i386.proposed"
   https://bugs.launchpad.net/bugs/1848200/+attachment/5303315/+files/gdb.i386.proposed

** Attachment added: "gdb.amd64"
   https://bugs.launchpad.net/bugs/1848200/+attachment/5303316/+files/gdb.amd64

** Attachment added: "gdb.amd64.proposed"
   https://bugs.launchpad.net/bugs/1848200/+attachment/5303317/+files/gdb.amd64.proposed

-- 
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to gdb in Ubuntu.
https://bugs.launchpad.net/bugs/1848200

Title:
  gdb not stopping on breakpoint in a 32-bit program

Status in gdb package in Ubuntu:
  Fix Released
Status in gdb source package in Bionic:
  Fix Committed

Bug description:
  [Impact]
  After upgrading gdb from 8.1-0ubuntu3 to 8.1-0ubuntu3.1, gdb does not stop
  on breakpoint when running a 32-bit application (on 64-bit Ubuntu).

  [Test Case]
  This can be reproduced with a simple “hello world” program:

  $ cat hello.c
  #include <stdio.h>
  int main()
  {
     // printf() displays the string inside quotation
     printf("Hello, World!");
     return 0;
  }
  $ gcc -ggdb -m32 hello.c
  $ gdb a.out
  (gdb) b hello.c:5
  Breakpoint 1 at 0x536: file hello.c, line 5.
  (gdb) run
  Starting program: /home/user/sandbox/a.out
  warning: Breakpoint address adjusted from 0xf7fd9be0 to 0xfffffffff7fd9be0.
  warning: Breakpoint address adjusted from 0xf7fda195 to 0xfffffffff7fda195.
  warning: Breakpoint address adjusted from 0xf7fdbd1c to 0xfffffffff7fdbd1c.
  warning: Breakpoint address adjusted from 0xf7fdb924 to 0xfffffffff7fdb924.
  warning: Breakpoint address adjusted from 0xf7fe99b3 to 0xfffffffff7fe99b3.
  warning: Breakpoint address adjusted from 0xf7fea401 to 0xfffffffff7fea401.
  warning: Breakpoint address adjusted from 0xf7fea706 to 0xfffffffff7fea706.

  --- (and not stopping nor outputting the text…) ---

  [Regression Risk]
  Test case ran on arm64 and regression tested using the above test case on amd64, i386 and s390x.

  This regression was fixed on the upstream gdb-8.1 branch within a few
  weeks of the breakage back in May 2018. Since then there have been no
  other fixes in this area on that branch, implying this fixed the issue
  and there were no further regressions discovered.

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



More information about the foundations-bugs mailing list