public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "mirzayanovmr at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/66095] New: Unexpected __gnu_cxx::__concurrence_lock_error with _GLIBCXX_DEBUG
Date: Sun, 10 May 2015 20:50:00 -0000	[thread overview]
Message-ID: <bug-66095-4@http.gcc.gnu.org/bugzilla/> (raw)

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=66095

            Bug ID: 66095
           Summary: Unexpected __gnu_cxx::__concurrence_lock_error with
                    _GLIBCXX_DEBUG
           Product: gcc
           Version: 4.9.2
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: c++
          Assignee: unassigned at gcc dot gnu.org
          Reporter: mirzayanovmr at gmail dot com
  Target Milestone: ---

Created attachment 35515
  --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=35515&action=edit
Code to reproduce a bug

The following code unexpectedly fails with error:

This application has requested the Runtime to terminate it in an unusual way.
Please contact the application's support team for more information.
terminate called after throwing an instance of
'__gnu_cxx::__concurrence_lock_error'
  what():  __gnu_cxx::__concurrence_lock_error


Used g++ version is 4.9.2 mingw-tdm:
A:\queue>g++ --version
g++.EXE (tdm-1) 4.9.2
Copyright (C) 2014 Free Software Foundation, Inc.
This is free software; see the source for copying conditions.  There is NO
warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.

The code is attached. You can compile it with g++ -O2 -static -o grnd grnd.cpp


             reply	other threads:[~2015-05-10 20:50 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-05-10 20:50 mirzayanovmr at gmail dot com [this message]
2024-02-08 12:46 ` [Bug libstdc++/66095] " redi 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-66095-4@http.gcc.gnu.org/bugzilla/ \
    --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).