public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "pcarlini at suse dot de" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libstdc++/24217] filebuf.open call sets the error bits incorrectly
Date: Thu, 06 Oct 2005 12:27:00 -0000 [thread overview]
Message-ID: <20051006122719.30261.qmail@sourceware.org> (raw)
In-Reply-To: <bug-24217-11468@http.gcc.gnu.org/bugzilla/>
------- Comment #1 from pcarlini at suse dot de 2005-10-06 12:27 -------
Hi. Certaintly, we cannot hope to debug further the issue without a proper,
self-contained, piece of code useful to reproduce the problem: this is a
strict requirement for any PR, in particular for very hard to reproduce
issues related to MT. That said, I'm afraid you are assuming a level of MT
safety that we don't (wo don't *want*, I would say, but this is very large
topic and the actual guarantees are also highly dependent on the underlying
libc, which we don't control, unfortunately) provide: for example, if running
your application single-threaded or protecting the filebuf operations with a
mutex avoids the problem, then very likely we would not consider the behavior
a bug.
--
pcarlini at suse dot de changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |WAITING
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=24217
next prev parent reply other threads:[~2005-10-06 12:27 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-10-05 17:10 [Bug c++/24217] New: " hemasai at yahoo dot com
2005-10-06 12:27 ` pcarlini at suse dot de [this message]
2005-10-06 18:12 ` [Bug libstdc++/24217] " hemasai at yahoo dot com
2005-10-06 18:32 ` pcarlini at suse dot de
2005-12-16 18:43 ` 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=20051006122719.30261.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).