From: Eli Zaretskii Newsgroups: comp.os.msdos.djgpp Subject: Re: Possible bash v2.03 file handle leak? Date: Sat, 08 Apr 2000 12:04:04 +0200 Organization: NetVision Israel Lines: 17 Message-ID: <38EF0414.6F1722D7@is.elta.co.il> References: <38ed4b38 DOT 5210950 AT news3 DOT banet DOT net> <200004071506 DOT LAA21108 AT indy DOT delorie DOT com> NNTP-Posting-Host: ras1-p97.rvt.netvision.net.il Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Trace: news.netvision.net.il 955188182 27791 62.0.172.99 (8 Apr 2000 10:03:02 GMT) X-Complaints-To: abuse AT netvision DOT net DOT il NNTP-Posting-Date: 8 Apr 2000 10:03:02 GMT X-Mailer: Mozilla 4.7 [en] (Win98; I) X-Accept-Language: en,ru,hebrew To: djgpp AT delorie DOT com DJ-Gateway: from newsgroup comp.os.msdos.djgpp Reply-To: djgpp AT delorie DOT com "Mark E." wrote: > > Eli Zaretskii wrote: > > >In any case, there's no `sopen' in the DJGPP library. So this > >function's sources are somewhere in the Bash distribution. > > > > FWIW, there is no 'sopen' function in the Bash source distribution that I > could find. Hmm. I cannot even find the error message (or any other string) that mentions `sopen' in Bash. Peter, could you please check again what does the error message say, exactly, and where does it come from? Is it possible that it comes from the script you are running, not from Bash itself?