Date: Thu, 7 Dec 2000 12:06:42 +0200 (IST) From: Eli Zaretskii X-Sender: eliz AT is To: djgpp AT delorie DOT com Subject: Re: popen hanging eventually In-Reply-To: <90lnb4$c8s$1@nnrp1.deja.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Reply-To: djgpp AT delorie DOT com Errors-To: nobody AT delorie DOT com X-Mailing-List: djgpp AT delorie DOT com X-Unsubscribes-To: listserv AT delorie DOT com Precedence: bulk On Wed, 6 Dec 2000 vonbane AT my-deja DOT com wrote: > i feel im getting closer, but still confused. i switched to a different > rsh program that logs what it is doing. it appears from the log that > rsh exits ok up until when popen has problems at that point rsh is not > even fired. it seems like popen is opening a file pointer to nowhere > and the command its supposed to be firing doesnt happen. I doubt that this analysis is correct, since elsewhere you told that pclose returns 4. That can happen only if the child program _was_ run and it returned an exit status of 4. But we don't need to guess; it's time to exploit the power of Free Software! I suggest to download v2/djlsr203.zip, extract the file src/libc/posix/stdio/popen.c from there, compile it with -g and link it with your program, then step with a debugger inside popen and see what exactly fails there, and how. If you post these details here, I'm sure we could get much closer to solving the problem.