From: Andrew Burgess <aburgess@redhat.com>
To: Aaron Merey <amerey@redhat.com>
Cc: gdb-patches@sourceware.org, Mark Wielaard <mark@klomp.org>
Subject: Re: [PATCH] gdb/debuginfod: cleanup debuginfod earlier
Date: Wed, 24 May 2023 15:33:11 +0100 [thread overview]
Message-ID: <875y8h7qag.fsf@redhat.com> (raw)
In-Reply-To: <CAJDtP-TvxuiZCGBjx3fmJdmyXkudpaqm9hSE0+9MBN63NqK1JQ@mail.gmail.com>
Aaron Merey <amerey@redhat.com> writes:
> On Tue, May 23, 2023 at 7:23 AM Andrew Burgess <aburgess@redhat.com> wrote:
>>
>> And then a global debuginfod_client_up is created to hold a pointer to
>> the debuginfod_client object. As a global this will be cleaned up
>> using the standard C++ global object destructor mechanism, which is
>> run after the at_exit handlers.
>>
>> However, it is expected that when debuginfod_end is called the
>> debuginfod_client object will still be in a usable state, that is, we
>> don't expect the at_exit handlers to have run and started cleaning up
>> the library state.
>
> The crash comes down to curl_multi_cleanup triggering a double free
> when it's called during process exit. Ideally this should be fixed in
> libcurl or at least the libcurl docs should mention that curl_multi_cleanup
> shouldn't be called at exit.
>
> But it's still a good idea to add this workaround to gdb.
It's only a workaround if libcurl doesn't just update their docs to say
don't call curl_multi_cleanup at exit! If they do that then debuginfod
needs to update its docs to say don't call debuginfod_end at exit
... and then we're back here, right?
> Thanks for looking
> into this. I tested Simon's patch since it's a bit simpler and it fixes the
> crash for me on F37.
Excellent, I'll add a commit message to Simon's version and repost it.
Thanks,
Andrew
>
>> There's no test associated with this patch. I have no idea how I
>> might trigger this bug from within the testsuite. If anyone has any
>> ideas then I'm happy to have a go at writing something.
>
> gdb's debuginfod tests only pull files from local servers. This crash
> does not reproduce when using a localhost URL. To test for this
> gdb would have to download from a remote server and maybe
> use the OPENSSL_CONF environment variable to set a custom
> config file path. However this might cause more problems than it
> solves.
>
> Aaron
next prev parent reply other threads:[~2023-05-24 14:33 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-23 11:23 Andrew Burgess
2023-05-23 12:31 ` Simon Marchi
2023-05-23 14:23 ` Aaron Merey
2023-05-24 14:33 ` Andrew Burgess [this message]
2023-06-08 13:33 ` [PATCHv2] " Andrew Burgess
2023-06-08 15:09 ` Mark Wielaard
2023-06-08 21:08 ` Aaron Merey
2023-06-09 14:24 ` Tom Tromey
2023-06-09 14:38 ` Andrew Burgess
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=875y8h7qag.fsf@redhat.com \
--to=aburgess@redhat.com \
--cc=amerey@redhat.com \
--cc=gdb-patches@sourceware.org \
--cc=mark@klomp.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).