From: Heribert Dahms <heribert_dahms@icon-scm.com>
To: 'Robert Collins' <robert.collins@itdomain.com.au>, cygwin@cygwin.com
Subject: RE: pthread: thread switching bug?
Date: Fri, 02 Nov 2001 15:49:00 -0000 [thread overview]
Message-ID: <BF35D9C143BCCC4EB63181B67C9320C804DEAD@serv-075.icon-germany.local> (raw)
Hi Rob,
I'd expect write() to be atomic, if "small" enough, but not print() or
fprintf()!
I once more cite APUE
(Richard W. Steven's Advanced Programming in the UNIX Environment),
chapter 10.6 Reentrant Functions:
"Most implementations of the standard I/O library
use global data structures in a nonreentrant way"
right under figure 10.3:
Reentrant functions that may be called from a signal handler.
Methinks this precaution applies also to MT!
Bye, Heribert (heribert_dahms@icon-scm.com)
> -----Original Message-----
> From: Robert Collins [SMTP:robert.collins@itdomain.com.au]
> Sent: Thursday, November 01, 2001 03:38
> To: cygwin@cygwin.com
> Subject: RE: pthread: thread switching bug?
>
> > -----Original Message-----
> > From: Christopher Faylor [ mailto:cgf@redhat.com ]
> > >Thanks for the testing, you've shown that there is non
> > thread safe code,
> > >probably in the fhandler_consoler in cygwin, or possibly in the MS
> > >Windows console code. Right now we don't know which.
> >
> > I'm still not sure why this is a cygwin bug. Is there some
> > requirement
> > that writes to the console be atomic? Your (Robert's) original email
> > indicated that the Opengroup spec didn't have this as a requirement.
>
> It's non expected behaviour at the least. At worst it could be a symptom
> of something more serious that is faulty. I intend to analyse it at some
> point.
>
> The Opengroup spec for printf doesn't document any thead safety needs,
> but, one would expect fprintf to a file to be atomic regardless of the
> actual file... There are separate thread considerations elsewhere in
> that tome, but I don't have time to dig them up right now.
>
> Rob
>
> --
> Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
> Bug reporting: http://cygwin.com/bugs.html
> Documentation: http://cygwin.com/docs.html
> FAQ: http://cygwin.com/faq/
--
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Bug reporting: http://cygwin.com/bugs.html
Documentation: http://cygwin.com/docs.html
FAQ: http://cygwin.com/faq/
next reply other threads:[~2001-11-02 15:49 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-11-02 15:49 Heribert Dahms [this message]
2001-11-02 18:38 ` Christopher Faylor
-- strict thread matches above, loose matches on Subject: below --
2001-10-31 18:30 Robert Collins
2001-10-31 18:36 ` Christopher Faylor
[not found] <3BCCB65E.77D66FE2@hszk.bme.hu>
2001-10-16 17:36 ` Christopher Faylor
2001-10-21 4:57 ` Robert Collins
[not found] ` <3BD72CC1.B2BF80D7@hszk.bme.hu>
2001-10-31 15:40 ` Robert Collins
2001-10-31 18:27 ` Christopher Faylor
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=BF35D9C143BCCC4EB63181B67C9320C804DEAD@serv-075.icon-germany.local \
--to=heribert_dahms@icon-scm.com \
--cc=cygwin@cygwin.com \
--cc=robert.collins@itdomain.com.au \
/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).