From: pjfarley AT banet DOT net (Peter J. Farley III)
Newsgroups: comp.os.msdos.djgpp
Subject: Re: Possible bash v2.03 file handle leak?
Date: Sat, 08 Apr 2000 01:58:12 GMT
Message-ID: <38ee90d5.1336038@news3.banet.net>
References: <Pine DOT SUN DOT 3 DOT 91 DOT 1000406132119 DOT 3003M-100000 AT is> <38ed4b38 DOT 5210950 AT news3 DOT banet DOT net> <200004071506 DOT LAA21108 AT indy DOT delorie DOT com>
X-Newsreader: Forte Free Agent 1.21/32.243
NNTP-Posting-Host: 32.100.85.50
X-Trace: 8 Apr 2000 01:56:30 GMT, 32.100.85.50
Organization: Global Network Services - Remote Access Mail & News Services
Lines: 16
X-Complaints-To: abuse AT prserv DOT net
To: djgpp AT delorie DOT com
DJ-Gateway: from newsgroup comp.os.msdos.djgpp
Reply-To: djgpp AT delorie DOT com

Eli Zaretskii <eliz AT delorie DOT com> wrote:
<Clear instructions on how to proceed snipped>
>In any case, there's no `sopen' in the DJGPP library.  So this
>function's sources are somewhere in the Bash distribution.

It turns out that "sopen" (actually "_awka_sopen") is part of the Awka
library, and the error message is being produced by that routine, so
my debugging job may be a tad easier.  I will set up a gdb.ini to
debug the Awka stuff first, and then worry about bash if it turns out
not to be an Awka problem.

Thanks again for the clear and concise help.  Much appreciated.

----------------------------------------------------
Peter J. Farley III (pjfarley AT nospam DOT dorsai DOT org OR
                     pjfarley AT nospam DOT banet DOT net)