public inbox for gdb-patches@sourceware.org
 help / color / mirror / Atom feed
From: Hannes Domani <ssbssa@yahoo.de>
To: "gdb-patches@sourceware.org" <gdb-patches@sourceware.org>
Subject: Re: [PATCH] Fix breakpoints on symbols with multiple trampoline symbols
Date: Tue, 5 Dec 2023 14:33:04 +0000 (UTC)	[thread overview]
Message-ID: <668233054.539577.1701786784066@mail.yahoo.com> (raw)
In-Reply-To: <1572481043.10136040.1700587686083@mail.yahoo.com>

 Ping.


Am Dienstag, 21. November 2023, 18:28:28 MEZ hat Hannes Domani <ssbssa@yahoo.de> Folgendes geschrieben:

> Ping.
>
>
> Am Montag, 6. November 2023, 20:31:22 MEZ hat Hannes Domani <ssbssa@yahoo.de> Folgendes geschrieben:
>
> > 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
> > ---
> > gdb/linespec.c | 4 ++++
> > 1 file changed, 4 insertions(+)
> >
> > diff --git a/gdb/linespec.c b/gdb/linespec.c
> > index fa733d880e3..2aa01819812 100644
> > --- a/gdb/linespec.c
> > +++ b/gdb/linespec.c
> > @@ -4281,6 +4281,10 @@ search_minsyms_for_name (struct collect_info *info,
> >           if (&item2 == &item)
> >         continue;
> >
> > +          /* Ignore other trampoline symbols.  */
> > +          if (item2.minsym->type () == mst_solib_trampoline)
> > +        continue;
> > +
> >           /* Trampoline symbols can only jump to exported
> >         symbols.  */
> >           if (msymbol_type_is_static (item2.minsym->type ()))
> > --
> > 2.35.1

  reply	other threads:[~2023-12-05 14:33 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20231106193047.2147-1-ssbssa.ref@yahoo.de>
2023-11-06 19:30 ` Hannes Domani
2023-11-21 17:28   ` Hannes Domani
2023-12-05 14:33     ` Hannes Domani [this message]
2023-12-05 15:21   ` Tom Tromey
2023-12-05 17:48     ` Hannes Domani

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=668233054.539577.1701786784066@mail.yahoo.com \
    --to=ssbssa@yahoo.de \
    --cc=gdb-patches@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).