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: Wed, 13 Jul 2022 11:15:09 +0000	[thread overview]
Message-ID: <bug-29311-4717-3ulMD7JGsC@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 #5 from Tom de Vries <vries at gcc dot gnu.org> ---
I tried to reproduce the problem outside gdb using:
...
$ cat test.c
#include <iconv.h>
#include <pthread.h>

const char *from = "UTF-8";
const char *to = "UTF-32LE";

static void
bar (void)
{
  int i;
  for (i = 0; i < 1000; ++i)
    {
      iconv_t handle = iconv_open (to, from);
      iconv_close (handle);
    }
}

static void *
foo (void *arg)
{
  bar ();
  return NULL;
}

int
main (void)
{
  pthread_t threadId;

  int i;
  for (i = 0; i < 4; ++i)
    {
      pthread_create (&threadId, NULL, &foo, NULL);
      pthread_detach (threadId);
    }

  bar ();

  return 0;
}
...
but no luck there.

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

  parent reply	other threads:[~2022-07-13 11:15 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
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 [this message]
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-3ulMD7JGsC@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).