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 breakpoints/29548] Can't breakpoint __cxa_throw with Qt5Core.dll
Date: Tue, 05 Dec 2023 17:47:32 +0000	[thread overview]
Message-ID: <bug-29548-4717-fRGUsroD2X@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-29548-4717@http.sourceware.org/bugzilla/>

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

--- Comment #1 from Sourceware Commits <cvs-commit at gcc dot gnu.org> ---
The master branch has been updated by Hannes Domani <ssbssa@sourceware.org>:

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

commit 6e28dd6fa3027d38351d2cf672509eca05aa19fd
Author: Hannes Domani <ssbssa@yahoo.de>
Date:   Tue Dec 5 18:41:44 2023 +0100

    Fix breakpoints on symbols with multiple trampoline symbols

    On mingw targets it's possible that there are multiple trampoline
    symbols for __cxa_throw, in each module where a throw is done, but
    without a corresponding global symbol.
    Since commit 77f2120b200be6cabbf6f610942fc1173a8df6d3 they cancel each
    other out in search_minsyms_for_name, which makes it impossible to set
    a breakpoint there:

    (gdb) b __cxa_throw
    Function "__cxa_throw" not defined.
    Make breakpoint pending on future shared library load? (y or [n]) y
    Breakpoint 2 (__cxa_throw) pending.
    (gdb) c
    Continuing.
    [Inferior 1 (process 10004) exited with code 03]

    With catch throw it also doesn't work, and you don't even get an error
    message:

    (gdb) catch throw
    Catchpoint 2 (throw)
    (gdb) c
    Continuing.
    [Inferior 1 (process 5532) exited with code 03]
    (gdb)

    The fix is to simply ignore other trampoline symbols when looking for
    corresponding global symbols, and it's working as expected:

    (gdb) b __cxa_throw
    Breakpoint 2 at 0x13f091590 (2 locations)
    (gdb) c
    Continuing.

    Breakpoint 2.1, 0x000000013f091590 in __cxa_throw ()
    (gdb)

    And catch throw also works again:

    (gdb) catch throw
    Catchpoint 2 (throw)
    (gdb) c
    Continuing.

    Catchpoint 2.1 (exception thrown), 0x000000013f181590 in __cxa_throw ()
    (gdb)

    Bug: https://sourceware.org/bugzilla/show_bug.cgi?id=29548
    Approved-By: Tom Tromey <tom@tromey.com>

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

  parent reply	other threads:[~2023-12-05 17:47 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-09-05 16:36 [Bug breakpoints/29548] New: " denis.zinin at gmail dot com
2022-09-11 15:07 ` [Bug breakpoints/29548] " ssbssa at sourceware dot org
2023-12-05 17:47 ` cvs-commit at gcc dot gnu.org [this message]
2023-12-05 17:49 ` ssbssa at sourceware dot 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-29548-4717-fRGUsroD2X@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).