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] [gdb] ThreadSanitizer: data race (/lib64/libtsan.so.2+0x4c5e2) in free
Date: Fri, 01 Jul 2022 08:16:06 +0000	[thread overview]
Message-ID: <bug-29311-4717-88ub1HkBmX@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-29311-4717@http.sourceware.org/bugzilla/>

https://sourceware.org/bugzilla/show_bug.cgi?id=29311

--- Comment #2 from Tom de Vries <vries at gcc dot gnu.org> ---
Created attachment 14188
  --> https://sourceware.org/bugzilla/attachment.cgi?id=14188&action=edit
LOG.txt

When trying to reproduce from the command line:
...
$ bash -x ./gdb.sh ./outputs/gdb.ada/char_enum_unicode/foo -batch -ex "break
foo.adb:26" 2>&1 | tee LOG.txt^C
...
I run into a different problem:
...
WARNING: ThreadSanitizer: data race (pid=30917)
  Write of size 8 at 0x7b0400004070 by main thread:
    #0 free <null> (libtsan.so.2+0x4c5e2)
    #1 xfree<char> /data/vries/gdb_versions/devel/src/gdb/../gdbsupport/gdb-x\
free.h:37 (gdb+0x650f17)
    #2 charset_vector::clear() /data/vries/gdb_versions/devel/src/gdb/charset\
.c:703 (gdb+0x651354)
    #3 charset_vector::~charset_vector() /data/vries/gdb_versions/devel/src/g\
db/charset.c:697 (gdb+0x6512d3)
    #4 <null> <null> (libtsan.so.2+0x32643)
    #5 captured_main_1 /data/vries/gdb_versions/devel/src/gdb/main.c:1310 (gd\
b+0xa3975a)

  Previous read of size 1 at 0x7b0400004072 by thread T1:
    [failed to restore the stack]
...

Same thing if I remove -batch and type quit instead.

So, is this a problem with

-- 
You are receiving this mail because:
You are on the CC list for the bug.

  parent reply	other threads:[~2022-07-01  8:16 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-07-01  8:08 [Bug gdb/29311] New: [gdb] ThreadSanitizer: data race (/lib64/libtsan.so.2+0x4c5e2) in free^M vries at gcc dot gnu.org
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 [this message]
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-88ub1HkBmX@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).