Re: Using -mno-cygwin causes different program behavior

Thanks both of you! In addition to a solution, I increased my understanding, which is even more valuable. -- View this message in context: http://www.nabble.com/Using--mno-cygwin-causes-different-program-behavior-tp20825507p20847165.html Sent from the Cygwin list mailing list archive

Using -mno-cygwin causes different program behavior

is your name?); line. Very strange! Any ideas on why this is happening? Thanks! -- View this message in context: http://www.nabble.com/Using--mno-cygwin-causes-different-program-behavior-tp20825507p20825507.html Sent from the Cygwin list mailing list archive at Nabble.com. -- Unsubscribe info

Re: Using -mno-cygwin causes different program behavior

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 According to C-Programmer on 12/3/2008 6:29 PM: But if I compile using the following command line argument: $ gcc -mno-cygwin -o ioProg1 ioProg1.c Then you are no longer using cygwin, and this is almost more of a question for the mingw list. I

RE: Using -mno-cygwin causes different program behavior

Eric Blake wrote on Thursday, December 04, 2008 1:42 AM:: According to C-Programmer on 12/3/2008 6:29 PM: But if I compile using the following command line argument: $ gcc -mno-cygwin -o ioProg1 ioProg1.c Then you are no longer using cygwin, and this is almost more of a question for the

Re: Using -mno-cygwin causes different program behavior

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 According to C-Programmer on 12/3/2008 6:29 PM: char name[25]; gets( name ); PS. This is a _disaster_ waiting to happen. You just coded a buffer overflow exploit, where someone can supply a name with more than 25 bytes, and in so doing,