This is the mail archive of the cygwin mailing list for the Cygwin project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

freopen irritates system-call/sh.exe


-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
 
Hi,
I posted a question a few days before, about sh.exe poping up
console-windows. I found out, that the use of
freopen causes the problem. So here is my modified question:

How does freopen-ing stdout and stderr affect subsequent "system" calls?

There must have been a change between Cygwin 1.5.10 and 1.5.19,
because the console windows didn't show up in Cygwin 1.5.10.
The freopen manpage states, that the original stream is closed when it
is assigned to the new file. So does freopen try to close the original
console output and what is the effect?

I'm sorry that I can't ask clearer or more specific but I'm really
puzzled by this. It is possible to rewite the code that contains
freopen with dup, dup2 calls but I'd like to understand what happened.

Regards
    Jens

- --
Dipl. Inform. Jens Wilken
Software Developer
OSC Embedded Systems AG
Industriestr. 11
26121 Oldenburg - Germany

Mail: Jens.Wilken@osc-es.de
Tel.: +49-441-350 42-0
Fax.: +49-441-350 42-364

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.0 (MingW32)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
 
iD8DBQFEK97X/nbz2tIAgUQRAoiSAKCQ+O1Rok7Fz4DjgcanOPCTO8JdGACeJxFl
EHed8bRIlMqlhaxnag3vQho=
=wHLS
-----END PGP SIGNATURE-----



--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Problem reports:       http://cygwin.com/problems.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]