From: "woodard at redhat dot com" <sourceware-bugzilla@sourceware.org>
To: elfutils-devel@sourceware.org
Subject: [Bug libdw/26921] dwarf_getalt () not thread-safe
Date: Sat, 21 Nov 2020 23:34:02 +0000 [thread overview]
Message-ID: <bug-26921-10460-Up3WKGvfh7@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-26921-10460@http.sourceware.org/bugzilla/>
https://sourceware.org/bugzilla/show_bug.cgi?id=26921
--- Comment #8 from Ben Woodard <woodard at redhat dot com> ---
One thing that I’m unclear about is how these two are different.
It doesn’t matter to me that they are split up but I just don’t understand
why?
-ben
On Sat, Nov 21, 2020 at 2:00 PM mark at klomp dot org <
sourceware-bugzilla@sourceware.org> wrote:
> https://sourceware.org/bugzilla/show_bug.cgi?id=26921
>
> --- Comment #7 from Mark Wielaard <mark at klomp dot org> ---
> Thanks for the backtraces, they show a different concurrent unsafe thing in
> libdw, the usage of (lazy) tsearch caches. I opened a separate bug for
> that,
> bug #26930
>
> --
> You are receiving this mail because:
> You are on the CC list for the bug.
>
>
--
You are receiving this mail because:
You are on the CC list for the bug.
next prev parent reply other threads:[~2020-11-21 23:34 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-19 16:22 [Bug libdw/26921] New: " mark at klomp dot org
2020-11-20 19:11 ` [Bug libdw/26921] " woodard at redhat dot com
2020-11-20 19:13 ` woodard at redhat dot com
2020-11-20 19:17 ` woodard at redhat dot com
2020-11-20 19:20 ` woodard at redhat dot com
2020-11-20 19:26 ` woodard at redhat dot com
2020-11-20 19:43 ` woodard at redhat dot com
2020-11-21 22:00 ` mark at klomp dot org
2020-11-21 23:34 ` woodard at redhat dot com [this message]
2020-11-21 23:53 ` mark at klomp dot org
2023-10-06 11:15 ` mark at klomp 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-26921-10460-Up3WKGvfh7@http.sourceware.org/bugzilla/ \
--to=sourceware-bugzilla@sourceware.org \
--cc=elfutils-devel@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).