[Bug python/19506] New: Regression with gdb.Breakpoint("*<addr>")

["kevin.pouget at gmail dot com" <sourceware-bugzilla at sourceware dot org>]

https://sourceware.org/bugzilla/show_bug.cgi?id=19506

            Bug ID: 19506
           Summary: Regression with gdb.Breakpoint("*<addr>")
           Product: gdb
           Version: HEAD
            Status: NEW
          Severity: normal
          Priority: P2
         Component: python
          Assignee: unassigned at sourceware dot org
          Reporter: kevin.pouget at gmail dot com
  Target Milestone: ---

With the HEAD version of gdb (7.10.50.20160120-git), there seem to be a
regression when setting Python breakpoints directly to a memory address :

> gdb.execute("start")
> main_addr = str(int(gdb.parse_and_eval("main").address)) # use int() on Py3 and long() on Py2
> gdb.execute("break *{}".format(main_addr))
> gdb.Breakpoint("*{}".format(main_addr))

Observed behavior
-----------------
(gdb 7.10.50.20160120-git)

>>> gdb.execute("break *{}".format(main_addr))
Breakpoint 2 at 0x401d20: file main.c, line 137.

>>> gdb.Breakpoint("*{}".format(main_addr))
Function "*4201760" not defined.
Breakpoint 3 (*4201760) pending.


Expected behavior
-----------------
(archlinux 7.10.1 and before)

> >>> gdb.execute("break *{}".format(main_addr))
> Breakpoint 2 at 0x401d20: file main.c, line 137.

> >>> gdb.Breakpoint("*{}".format(main_addr))
> Breakpoint 3 at 0x401d20: file main.c, line 137.

-- 
You are receiving this mail because:
You are on the CC list for the bug.