public inbox for gdb-prs@sourceware.org
help / color / mirror / Atom feed
From: "cvs-commit at gcc dot gnu.org" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug testsuite/29910] [gdb/testsuite] FAIL: gdb.python/py-breakpoint.exp: test_hardware_breakpoints: Set hardware breakpoint
Date: Mon, 02 Jan 2023 10:59:22 +0000	[thread overview]
Message-ID: <bug-29910-4717-b6sma5uVJ7@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-29910-4717@http.sourceware.org/bugzilla/>

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

--- Comment #2 from cvs-commit at gcc dot gnu.org <cvs-commit at gcc dot gnu.org> ---
The master branch has been updated by Tom de Vries <vries@sourceware.org>:

https://sourceware.org/git/gitweb.cgi?p=binutils-gdb.git;h=b9877acc81ade609c503bbcff064e09d3e290a84

commit b9877acc81ade609c503bbcff064e09d3e290a84
Author: Tom de Vries <tdevries@suse.de>
Date:   Mon Jan 2 11:59:17 2023 +0100

    [gdb/testsuite] Fix gdb.python/py-breakpoint.exp with libstdc++ debug info

    On x86_64-linux, I run into:
    ...
    (gdb) python hbp1 = gdb.Breakpoint("add",
type=gdb.BP_HARDWARE_BREAKPOINT)^M
    Hardware assisted breakpoint 2 at 0x40072e: add. (7 locations)^M
    (gdb) FAIL: gdb.python/py-breakpoint.exp: test_hardware_breakpoints: \
      Set hardware breakpoint
    ...
    due to libstdc++ debug info:
    ...
    $ gdb -q -batch outputs/gdb.python/py-breakpoint/py-breakpoint \
      -ex start \
      -ex "b add" \
      -ex "info break"
    Temporary breakpoint 1 at 0x40076a: file py-breakpoint.c, line 50.

    Temporary breakpoint 1, main (argc=1, argv=$hex) at py-breakpoint.c:50
    50        int foo = 5;
    Breakpoint 2 at 0x40072e: add. (7 locations)
    Num     Type           Disp Enb Address            What
    2       breakpoint     keep y   <MULTIPLE>
    2.1                         y   0x000000000040072e in add(int) at \
      py-breakpoint.c:39
    2.2                         y   0x00007ffff7b131de in \
      (anonymous namespace)::fast_float::bigint::add at \
      ../../../../../libstdc++-v3/src/c++17/fast_float/fast_float.h:1815
      ...
    2.7                         y   0x00007ffff7b137e4 in \
      (anonymous namespace)::fast_float::bigint::add at \
      ../../../../../libstdc++-v3/src/c++17/fast_float/fast_float.h:1815
    ...

    Fix this by using qualified=True.

    Tested on x86_64-linux.
    PR testsuite/29910
    Bug: https://sourceware.org/bugzilla/show_bug.cgi?id=29910

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

  parent reply	other threads:[~2023-01-02 10:59 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-12-16 15:10 [Bug testsuite/29910] New: " vries at gcc dot gnu.org
2023-01-02  9:14 ` [Bug testsuite/29910] " vries at gcc dot gnu.org
2023-01-02 10:59 ` cvs-commit at gcc dot gnu.org [this message]
2023-01-02 11:00 ` vries at gcc dot gnu.org

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=bug-29910-4717-b6sma5uVJ7@http.sourceware.org/bugzilla/ \
    --to=sourceware-bugzilla@sourceware.org \
    --cc=gdb-prs@sourceware.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).