public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: cwitty@newtonlabs.com (Carl R. Witty)
To: nobody@gcc.gnu.org
Cc: gcc-prs@gcc.gnu.org,
Subject: Re: libstdc++/9069: race condition in libstdc++3 (basic_string.tcc)
Date: Thu, 13 Feb 2003 02:16:00 -0000	[thread overview]
Message-ID: <20030213021600.27705.qmail@sources.redhat.com> (raw)

The following reply was made to PR libstdc++/9069; it has been noted by GNATS.

From: cwitty@newtonlabs.com (Carl R. Witty)
To: bkoz@gcc.gnu.org
Cc: 140201@bugs.debian.org, gcc-bugs@gcc.gnu.org, gcc-prs@gcc.gnu.org,
   cwitty@newtonlabs.com, gcc-gnats@gcc.gnu.org
Subject: Re: libstdc++/9069: race condition in libstdc++3 (basic_string.tcc)
Date: 12 Feb 2003 18:10:10 -0800

 bkoz@gcc.gnu.org writes:
 
 > Synopsis: race condition in libstdc++3 (basic_string.tcc)
 > 
 > State-Changed-From-To: open->analyzed
 > State-Changed-By: bkoz
 > State-Changed-When: Mon Jan  6 12:49:46 2003
 > State-Changed-Why:
 >     Can example code that demonstrates this problem be provided please? I'd like to add it to the thread testcase if possible.
 >     
 >     As a general rule, MT bugs always need a test case before a patch can be developed and a fix can be applied.
 >     
 >     thanks,
 >     benjamin
 > 
 > http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&database=gcc&pr=9069
 
 I never had a test case for this; I saw the problem by examining the
 source code.
 
 Carl Witty


             reply	other threads:[~2003-02-13  2:16 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-02-13  2:16 Carl R. Witty [this message]
  -- strict thread matches above, loose matches on Subject: below --
2003-02-13  9:36 Christian Ehrhardt
2003-02-13  5:16 Benjamin Kosnik
2003-01-06 20:49 bkoz
2002-12-27 13:46 Matthias Klose

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=20030213021600.27705.qmail@sources.redhat.com \
    --to=cwitty@newtonlabs.com \
    --cc=gcc-prs@gcc.gnu.org \
    --cc=nobody@gcc.gnu.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).