From: Simon Marchi <simon.marchi@polymtl.ca>
To: Kevin Buettner <kevinb@redhat.com>, Tom Tromey <tom@tromey.com>
Cc: Florian Weimer <fweimer@redhat.com>, gdb-patches@sourceware.org
Subject: Re: [PATCH] gdb: try to load libthread_db only after reading all shared libraries when attaching
Date: Tue, 6 Apr 2021 22:49:50 -0400 [thread overview]
Message-ID: <d35d8713-3a01-126f-6f8e-4a9f40feb3fb@polymtl.ca> (raw)
In-Reply-To: <20210406140847.038a7431@f33-m1.lan>
On 2021-04-06 5:08 p.m., Kevin Buettner via Gdb-patches wrote:
> On Fri, 02 Apr 2021 11:14:23 -0600
> Tom Tromey <tom@tromey.com> wrote:
>
>> Also, does gdbserver need a similar treatment? I know it has to load
>> libthread_db (one of the problems with this library) but is the decision
>> to do so drive by gdb or by itself? I don't recall.
>
> gdbserver definitely has problems too. It needs gdb to look up
> symbols (via the qSymbol packet), but is only able to do so at certain
> times.
>
> I'm trying to puzzle it out now...
Hi Kevin,
Just wondering, are you actively working on this problem? I am not
currently assigned on this at $day_job, so all I can put on it is
leftovers of time here and there. If you want to propose another patch
/ solution, feel free!
Simon
next prev parent reply other threads:[~2021-04-07 2:49 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-30 17:21 Simon Marchi
2021-04-02 17:14 ` Tom Tromey
2021-04-06 21:08 ` Kevin Buettner
2021-04-07 2:49 ` Simon Marchi [this message]
2021-04-07 23:51 ` Kevin Buettner
2021-04-07 2:45 ` Simon Marchi
2021-04-08 18:46 ` Tom Tromey
2021-05-04 18:02 ` [PATCH v2] gdb: try to load libthread_db only after reading all shared libraries when attaching / handling a fork child Simon Marchi
2021-05-30 14:12 ` Joel Brobecker
2021-05-31 0:48 ` Simon Marchi
2021-06-04 22:42 ` Kevin Buettner
2021-06-08 20:59 ` Simon Marchi
2021-06-08 21:28 ` Carlos O'Donell
2021-06-08 21:53 ` Kevin Buettner
2021-06-09 6:39 ` Florian Weimer
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=d35d8713-3a01-126f-6f8e-4a9f40feb3fb@polymtl.ca \
--to=simon.marchi@polymtl.ca \
--cc=fweimer@redhat.com \
--cc=gdb-patches@sourceware.org \
--cc=kevinb@redhat.com \
--cc=tom@tromey.com \
/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).