Path: utzoo!utgpu!attcan!uunet!nuchat!moray!urchin!f506.n106.z1.fidonet.org!Roy.Browning From: Roy.Browning@f506.n106.z1.fidonet.org (Roy Browning) Newsgroups: comp.lang.c++ Subject: Once again, Zortech C++ problem Message-ID: <19036.24E341B0@urchin.fidonet.org> Date: 10 Aug 89 02:16:35 GMT Sender: ufgate@urchin.fidonet.org (newsout1.26) Organization: FidoNet node 1:106/506 - Fulcrum's Edge, Spring TX Lines: 24 > From: rchen@m.cs.uiuc.edu > Date: 8 Aug 89 06:01:00 GMT > Message-ID: <4800069@m.cs.uiuc.edu> > Newsgroups: comp.lang.c++ > Does anyone has problems with fgl.lib in Zortech C++ (1.06 and 1.07)? > To be more specific, has anyone seen the error message: > "FATAL ERROR: x coordinate out of range. TABELS.ASM line 107." ? > shaky, i.e. the program becomes code sensitive (scary, isn't it?). > Calling a subroutine (not necessarily a specific one) once would be > different from calling it twice (one crashes the system and the other Ron: I only have about 5 years 'C' experience but hopefully I can make a suggestion that hasn't already been covered. Recently I caught myself trying to delete a character array that was stored on the stack. Every time the "String" destructor was being called It was generating allocation errors. I've since added a "stack flag" to avoid this problem. In the past EVERYTIME a program of mine worked intermittantly or generated random errors I traced the problem back to a coding error introduced by myself. Compiler bugs are usually consistant. If you can reduce the program to the essential functions that produce the error I will try to locate the trouble. Sometimes it requires unfamiliar eyes to spot a mistake. And if my eyes can't spot it then we'll try Bob Stout's, an avid Zortechie. BBSystem at (713)350-6284 in case my origin line gets truncated. However Joe Huffman (graphics library) frequents Walter's Board at (206)821-2123. He might be able to help you islotate the problem's source. Roy Browning