[Bug 1848200] Re: gdb not stopping on breakpoint in a 32-bit program

[James Foster]

*** This bug is a duplicate of bug 1846557 ***
    https://bugs.launchpad.net/bugs/1846557

Will this have been fixed in "GNU gdb (Ubuntu 9.2-0ubuntu1~20.04) 9.2"?
I'm having similar problems and came across this report claiming that it
is fixed in "8.1-0ubuntu3.2". I don't understand how the numbers work
but assume that 9.2 has fixes that were in 8.1. If not, then that would
explain my problem.

-- 
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 Released

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