From: Tom Tromey <tom@tromey.com>
To: Tom de Vries <tdevries@suse.de>
Cc: gdb-patches@sourceware.org
Subject: Re: [PATCH][gdb] Fix internal-error in process_event_stop_test
Date: Thu, 07 Jan 2021 13:10:37 -0700 [thread overview]
Message-ID: <87y2h4v77m.fsf@tromey.com> (raw)
In-Reply-To: <20210105132923.GA15843@delia> (Tom de Vries's message of "Tue, 5 Jan 2021 14:29:24 +0100")
>>>>> "Tom" == Tom de Vries <tdevries@suse.de> writes:
Tom> Fix this by only trying to install the master exception breakpoint in
Tom> libgcc.debug using the _Unwind_DebugHook method, if the install using probes
Tom> in libgcc failed.
This seems like a reasonable idea.
Tom> Any comments?
I suspect this would be a bit shorter if the loop only examined
"primary" objfiles (ones that don't have a backlink) and then delegated
to a helper function that did the search. What do you think?
Tom
next prev parent reply other threads:[~2021-01-07 20:10 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-05 13:29 Tom de Vries
2021-01-07 20:10 ` Tom Tromey [this message]
2021-01-08 5:23 ` Tom de Vries
2021-02-02 18:25 ` Hafiz Abid Qadeer
2021-02-03 9:55 ` Tom de Vries
2021-02-03 10:58 ` Hafiz Abid Qadeer
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=87y2h4v77m.fsf@tromey.com \
--to=tom@tromey.com \
--cc=gdb-patches@sourceware.org \
--cc=tdevries@suse.de \
/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