public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: "Jonathan Pryor" <jonpryor@vt.edu>
To: "Cygwin Mailing List" <cygwin@sourceware.cygnus.com>
Subject: Compiled executable differences between 9x and NT
Date: Wed, 31 Mar 1999 19:45:00 -0000	[thread overview]
Message-ID: <088201be696e$f2867650$e63d2509@jonpryor.raleigh.ibm.com> (raw)
Message-ID: <19990331194500.1_1-3vg5ybM8sY1aQQI0Rc6ktsWt4R-PabYVfX0nSPw@z> (raw)

(I would try to look this up on the web page, but 
I'm having trouble connecting to cygnus.com at the
moment...)

What are the *exact* differences between 95 and NT,
as far as the cygwin environment and compiler are
concerned?

I would normally assume that if I stick with the
strict ANSI stuff (console I/O), limited to the
extent so that MSVC can also compile it (no great
reliance on the posix api's), that I should be able
to compile an executable on both 95 and NT and have
it behave the same on both.

Unfortunately, I have a program for which this isn't 
happening.  Under NT, it runs as expected in all 
cases.  Under 95, it's currently causing
a "blue screen" with cygwin egcs-1.1.1, and causes
a "This progam has performed an illegal operation
and will be shut down." message under mingw32.

I get these errors if the executable was compiled
and run under 95, or if the executable was compiled
under NT but run under 95.  (The same executable -- 
compiled under either 95 or NT -- runs fine under
NT.)

As a note, it compiles and runs fine with MSVC6.

Any thoughts as to what could be causing the problem?
Is there anything that is known to break 95 while
working under NT?

Thanks,
 - Jon

(Yes, I probably should try to get the whole source
available, but I'm in the process of trying to clean
it up for public distribution, so it may be awhile...)


--
Want to unsubscribe from this list?
Send a message to cygwin-unsubscribe@sourceware.cygnus.com


             reply	other threads:[~1999-03-31 19:45 UTC|newest]

Thread overview: 34+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1999-03-08  6:21 Jonathan Pryor [this message]
     [not found] ` < 088201be696e$f2867650$e63d2509@jonpryor.raleigh.ibm.com >
1999-03-09 12:20   ` Geoffrey Noer
1999-03-31 19:45     ` Geoffrey Noer
1999-03-09 12:27   ` Mumit Khan
1999-03-31 19:45     ` Mumit Khan
1999-03-31 19:45 ` Jonathan Pryor
1999-03-08 18:37 N8TM
1999-03-31 19:45 ` N8TM
1999-03-09  5:43 Jonathan Pryor
1999-03-31 19:45 ` Jonathan Pryor
1999-03-09 15:19 Jonathan Pryor
     [not found] ` < 0ac501be6a83$48632630$e63d2509@jonpryor.raleigh.ibm.com >
1999-03-09 17:07   ` Mumit Khan
1999-03-31 19:45     ` Mumit Khan
1999-03-31 19:45 ` Jonathan Pryor
1999-03-10  4:59 Jonathan Pryor
1999-03-11  7:03 ` Anders Norlander
     [not found]   ` < 36E7DAFC.7D1AE3AC@hem2.passagen.se >
1999-03-11  7:08     ` Mumit Khan
1999-03-11  7:17       ` neud
1999-03-31 19:45         ` neud
     [not found]       ` < 199903111508.JAA27393@modi.xraylith.wisc.edu >
1999-03-11 19:14         ` Glenn Spell
1999-03-31 19:45           ` Glenn Spell
1999-03-31 19:45       ` Mumit Khan
1999-03-31 19:45   ` Anders Norlander
1999-03-31 19:45 ` Jonathan Pryor
1999-03-11  7:37 Jonathan Pryor
1999-03-31 19:45 ` Jonathan Pryor
1999-03-12  5:17 Jonathan Pryor
     [not found] ` < 0f3801be6c8a$9c41d7c0$e63d2509@jonpryor.raleigh.ibm.com >
1999-03-12 10:58   ` Glenn Spell
1999-03-31 19:45     ` Glenn Spell
1999-03-31 19:45 ` Jonathan Pryor
1999-03-12  6:06 Suhaib M. Siddiqi
1999-03-31 19:45 ` Suhaib M. Siddiqi
1999-03-12 11:57 Jonathan Pryor
1999-03-31 19:45 ` Jonathan Pryor

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='088201be696e$f2867650$e63d2509@jonpryor.raleigh.ibm.com' \
    --to=jonpryor@vt.edu \
    --cc=cygwin@sourceware.cygnus.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).