From: "mail at milianw dot de" <sourceware-bugzilla@sourceware.org>
To: elfutils-devel@sourceware.org
Subject: [Bug libdw/26930] tsearch/tfind tree caches need locking
Date: Tue, 24 Nov 2020 12:17:21 +0000 [thread overview]
Message-ID: <bug-26930-10460-iUCya1HAFK@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-26930-10460@http.sourceware.org/bugzilla/>
https://sourceware.org/bugzilla/show_bug.cgi?id=26930
Milian Wolff <mail at milianw dot de> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |mail at milianw dot de
--- Comment #1 from Milian Wolff <mail at milianw dot de> ---
as a suggestion to catch and fix these issues: if there'd be a unit test that
runs through the "supposedly thread safe" API, one could compile it with tsan
and verify that the code is actually thread safe. with elfutils using plain c,
tsan should work pretty well from what I know.
--
You are receiving this mail because:
You are on the CC list for the bug.
next prev parent reply other threads:[~2020-11-24 12:17 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-21 21:58 [Bug libdw/26930] New: " mark at klomp dot org
2020-11-24 12:17 ` mail at milianw dot de [this message]
2023-10-06 11:16 ` [Bug libdw/26930] " 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-26930-10460-iUCya1HAFK@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).