public inbox for gdb-prs@sourceware.org
help / color / mirror / Atom feed
From: "vries at gcc dot gnu.org" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug gdb/29311] New: [gdb] ThreadSanitizer: data race (/lib64/libtsan.so.2+0x4c5e2) in free^M
Date: Fri, 01 Jul 2022 08:08:20 +0000 [thread overview]
Message-ID: <bug-29311-4717@http.sourceware.org/bugzilla/> (raw)
https://sourceware.org/bugzilla/show_bug.cgi?id=29311
Bug ID: 29311
Summary: [gdb] ThreadSanitizer: data race
(/lib64/libtsan.so.2+0x4c5e2) in free^M
Product: gdb
Version: HEAD
Status: NEW
Severity: normal
Priority: P2
Component: gdb
Assignee: unassigned at sourceware dot org
Reporter: vries at gcc dot gnu.org
Target Milestone: ---
I build gdb with gcc 12.1.0 (system gcc) and -fsanitize=thread on openSUSE
(with system glibc 2.35) Tumbleweed, and ran the testsuite, and ran into issues
with gdb.ada/char_enum_unicode.exp:
...
WARNING: ThreadSanitizer: data race (pid=21301)^M
Write of size 8 at 0x7b2000008080 by main thread:^M
#0 free <null> (libtsan.so.2+0x4c5e2)^M
#1 _dl_close_worker <null> (ld-linux-x86-64.so.2+0x4b7b)^M
#2 convert_between_encodings(char const*, char const*, unsigned char
const*, unsigned int, int, obstack*, transliterations)
/data/vries/gdb_versions/devel/src/gdb/charset.c:584 (gdb+0x64fc37)^M
...
^M
Previous write of size 8 at 0x7b2000008080 by thread T1:^M
[failed to restore the stack]^M
...
--
You are receiving this mail because:
You are on the CC list for the bug.
next reply other threads:[~2022-07-01 8:08 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-01 8:08 vries at gcc dot gnu.org [this message]
2022-07-01 8:09 ` [Bug gdb/29311] " vries at gcc dot gnu.org
2022-07-01 8:09 ` [Bug gdb/29311] [gdb] ThreadSanitizer: data race (/lib64/libtsan.so.2+0x4c5e2) in free vries at gcc dot gnu.org
2022-07-01 8:16 ` vries at gcc dot gnu.org
2022-07-01 8:17 ` vries at gcc dot gnu.org
2022-07-13 10:58 ` vries at gcc dot gnu.org
2022-07-13 11:15 ` vries at gcc dot gnu.org
2022-07-14 7:07 ` vries at gcc dot gnu.org
2022-07-14 7:07 ` vries at gcc dot gnu.org
2022-07-14 18:49 ` vries at gcc dot gnu.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-29311-4717@http.sourceware.org/bugzilla/ \
--to=sourceware-bugzilla@sourceware.org \
--cc=gdb-prs@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).