delorie.com/archives/browse.cgi   search  
Mail Archives: djgpp/1997/05/26/13:34:05

From: mert0407 AT sable DOT ox DOT ac DOT uk (George Foot)
Newsgroups: comp.os.msdos.djgpp
Subject: Re: Windows NT
Date: 26 May 1997 12:20:12 GMT
Organization: Oxford University, England
Lines: 26
Message-ID: <5mbv5s$hgf@news.ox.ac.uk>
References: <Pine DOT SUN DOT 3 DOT 91 DOT 970525140343 DOT 4960X-100000 AT is> <5ma1v2$avb AT freenet-news DOT carleton DOT ca>
NNTP-Posting-Host: sable.ox.ac.uk
To: djgpp AT delorie DOT com
DJ-Gateway: from newsgroup comp.os.msdos.djgpp

Paul Derbyshire (ao950 AT FreeNet DOT Carleton DOT CA) wrote:

: Sounds like maybe if DJGPP's exception handlers catch it, the bug's in
: your code, but if you get a *Windows* exception message (dialog, "illegal
: operation" blah blah) the bug might be in Windows code...?

This brings up a problem I have had for a very long time; the machines I
have to use to access the internet (like now) do not have DJGPP on them.
To compile programs I have been using DJ's web based compiler. However,
attempting to run programs frequently fails. One of four things happens:
either the program runs fine, or it gives the standard traceback
information, or it makes Windows 95 barf and close the DOS box, or (most
strange of all) it does nothing - no error, no output, nothing.

The connection to what Paul's saying is that I know the program is correct
(it's the simple "Hello, World!\n" example that's in the compiler
initially, with the #include corrected), yet I still sometimes get the
regular DJGPP-style traceback. This must be a problem with the Win95 setup
here. So it indicates that a dodgy Windows DPMI server won't necessarily
cause the Windows-style crash.

-- 
George Foot <mert0407 AT sable DOT ox DOT ac DOT uk>
Merton College, Oxford

What's the wizard's password for? (dunnet)

- Raw text -


  webmaster     delorie software   privacy  
  Copyright © 2019   by DJ Delorie     Updated Jul 2019