public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "l_heldt at poczta dot onet dot pl" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libstdc++/29496] _M_invalidate function is not thread-safe in GLIBCXX_DEBUG mode
Date: Thu, 19 Oct 2006 13:51:00 -0000 [thread overview]
Message-ID: <20061019135146.29074.qmail@sourceware.org> (raw)
In-Reply-To: <bug-29496-9884@http.gcc.gnu.org/bugzilla/>
------- Comment #7 from l_heldt at poczta dot onet dot pl 2006-10-19 13:51 -------
(In reply to comment #2)
> Please attach a complete test case, not a sketch.
>
> -benjamin
>
This bug is a pure race-condition. There is no test case which would reveal it
with a 100% certainty. I have noticed the bug after receiving strange SIGSEGV
in _M_invalidate() function. After reviewing the code I found the problem
stated in this bug report.
Of course you can say: "No test case - no bug" but I guess this would be a very
naive approach.
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=29496
next prev parent reply other threads:[~2006-10-19 13:51 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-10-18 8:33 [Bug c++/29496] New: " l_heldt at poczta dot onet dot pl
2006-10-18 9:01 ` [Bug libstdc++/29496] " pcarlini at suse dot de
2006-10-18 9:43 ` bkoz at gcc dot gnu dot org
2006-10-18 10:06 ` pcarlini at suse dot de
2006-10-18 10:40 ` pcarlini at suse dot de
2006-10-18 14:40 ` grzes at nec-labs dot com
2006-10-18 15:56 ` bkoz at gcc dot gnu dot org
2006-10-19 13:51 ` l_heldt at poczta dot onet dot pl [this message]
2006-10-31 11:12 ` l_heldt at poczta dot onet dot pl
2006-10-31 11:38 ` pcarlini at suse dot de
2006-10-31 11:47 ` pcarlini at suse dot de
2006-10-31 11:49 ` pcarlini at suse dot de
2006-10-31 12:19 ` pcarlini at suse dot de
2006-10-31 13:12 ` l_heldt at poczta dot onet dot pl
2006-10-31 13:23 ` pcarlini at suse dot de
2006-10-31 13:42 ` l_heldt at poczta dot onet dot pl
2006-10-31 13:46 ` pcarlini at suse dot de
2006-10-31 14:30 ` pcarlini at suse dot de
2006-10-31 14:37 ` bkoz at gcc dot gnu dot org
2006-10-31 16:32 ` pcarlini at suse dot de
2006-10-31 17:01 ` pcarlini at suse dot de
2006-10-31 17:24 ` l_heldt at poczta dot onet dot pl
2006-10-31 23:53 ` pcarlini at suse dot de
2006-11-01 22:42 ` pcarlini at suse dot de
2006-11-11 17:32 ` paolo at gcc dot gnu dot org
2006-11-11 17:36 ` pcarlini at suse dot de
2006-12-01 1:07 ` chaoyingfu at gcc dot gnu dot org
2007-02-01 15:57 ` pcarlini at suse dot de
2007-02-01 15:57 ` paolo at gcc dot gnu dot org
2007-05-14 21:36 ` pcarlini at suse dot de
2007-05-14 21:37 ` mmitchel at gcc dot gnu dot org
2007-05-14 21:39 ` pcarlini at suse dot de
2007-05-14 21:39 ` pcarlini at suse dot de
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=20061019135146.29074.qmail@sourceware.org \
--to=gcc-bugzilla@gcc.gnu.org \
--cc=gcc-bugs@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).