From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 14885 invoked by alias); 19 Dec 2003 14:54:16 -0000 Mailing-List: contact ecos-discuss-help@sources.redhat.com; run by ezmlm Precedence: bulk List-Subscribe: List-Archive: List-Post: List-Help: , Sender: ecos-discuss-owner@sources.redhat.com Received: (qmail 13651 invoked from network); 19 Dec 2003 14:54:10 -0000 Received: from unknown (HELO msgdirector2.onetel.net.uk) (212.67.96.149) by sources.redhat.com with SMTP; 19 Dec 2003 14:54:10 -0000 Received: from miso.calivar.com (213-78-84-211.friaco.onetel.net.uk [213.78.84.211]) by msgdirector2.onetel.net.uk (Mirapoint Messaging Server MOS 3.3.6-GR) with ESMTP id AQK42623; Fri, 19 Dec 2003 14:53:53 GMT Received: from miso.calivar.com (miso.calivar.com [127.0.0.2]) by miso.calivar.com (Postfix) with ESMTP id 8213428DF45; Fri, 19 Dec 2003 14:53:52 +0000 (GMT) To: "sandeep" Cc: , "Ecos-Discuss" Cc: jifl@eCosCentric.com References: <00fd01c3c5f6$4fbeb1f0$2564a8c0@blackmagic> From: Nick Garnett Date: Fri, 19 Dec 2003 17:51:00 -0000 In-Reply-To: <00fd01c3c5f6$4fbeb1f0$2564a8c0@blackmagic> Message-ID: User-Agent: Gnus/5.09 (Gnus v5.9.0) Emacs/21.2 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Subject: Re: [ECOS] Thread safe in libc file stream X-SW-Source: 2003-12/txt/msg00284.txt.bz2 "sandeep" writes: > > Can anybody comment on this? Am I missing something or is this a bug in > > ecos? Anybody going to have an official solution for this? > > > > -----Original Message----- > > From: ecos-discuss-owner@sources.redhat.com > > [mailto:ecos-discuss-owner@sources.redhat.com]On Behalf Of Yuxin Jiang > > Sent: Wednesday, December 10, 2003 11:56 AM > > To: Ecos-Discuss > > Subject: [ECOS] Thread safe in libc file stream > > > > It seems to me that the function cyg_libc_stdio_flush_all_but( > > Cyg_StdioStream *not_this_stream ) is not thread-safe. > === snipped ==== > > I haven't gone through your earlier mail thoroughly, but I suspect > not-thread-safe code possibillities there in that section. > Few days back (before readdir thread-safeness issue was suspected and posted on > list, 12 Dec 2003) we had encountered an issue that was showing up in > cyg_libc_stdio_flush_all_but, but on later analysis it was tracked down to > beginning from readdir call (and going into details of your post got pushed down > the stack wrt other chorus). > I guess Nick might be too busy these days, otherwise he would have responded to > earlier such posts analytically. In between you can analyse your observation and > track the root cause of problem that is manifesting itself in the observed > place. I have been busy, and still am, so I don't really have time to go through the original post at present. Also, Jonathan is really the right person to respond since he wrote the code. However, he is also very busy. I hope he will find some time to respond, but don't hold your breath :-) -- Nick Garnett eCos Kernel Architect http://www.ecoscentric.com The eCos and RedBoot experts -- Before posting, please read the FAQ: http://sources.redhat.com/fom/ecos and search the list archive: http://sources.redhat.com/ml/ecos-discuss