Xref: utzoo comp.lang.c:5971 comp.sys.ibm.pc:10128
Path: utzoo!mnetor!uunet!husc6!hao!oddjob!uwvax!umn-d-ub!umn-cs!ems!rosevax!richw
From: richw@rosevax.Rosemount.COM (Rich Wagenknecht)
Newsgroups: comp.lang.c,comp.sys.ibm.pc
Subject: QC problems
Message-ID: <3790@rosevax.Rosemount.COM>
Date: 4 Jan 88 21:49:40 GMT
Organization: Rosemount Inc., Eden Prairie, MN
Lines: 19
Keywords: MS, QC


  I've found what appears to be a very strange problem with MS QC 1.0.
I've developed some windowing software which makes extensive use of
far character arrays and the movedate function. I originally developed
the software under QC 1.0 using the in memory compilation option. The
software worked well and I was ready to compile to an executable file.
I compiled using the executable option and again all went well (ie no
compiler warnings or sneezes). When I ran the executable my machine
went completely wild and locked up. Hmm. I've now spent several days
tracing over my source code looking for wild pointers etc. Nothing.
The software runs perfectly under QC with in memory compilation but will
not run when compiled to an executable using QC or MSC 5.0. Now, it
could very well be that my code is at fault. However, QC 1.0 is useless
to me because it does run my software in memory without any problems!
Notice that I have not said that MS is at fault. I just can't understand
how my software could run under QC but not as a stand alone executable.
Has anyone else experienced anything similar?

Rich W