Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!sdd.hp.com!elroy.jpl.nasa.gov!decwrl!borland.com!sidney From: sidney@borland.com (Sidney Markowitz) Newsgroups: comp.os.msdos.programmer Subject: Re: Stack Overflow! tc++ Message-ID: <1991Mar7.001520.27278@borland.com> Date: 7 Mar 91 00:15:20 GMT References: <902@masterCNA.TEK.COM> Organization: Borland International Lines: 42 In article <902@masterCNA.TEK.COM> waynet@kit.tek.com (Wayne Turner) writes: >Subject: Re: Stack Overflow! tc++ > >In article <1991Mar6.135439.22464@murdoch.acc.Virginia.EDU> pts@faraday.clas.Virginia.EDU (Paul T. Shannon) writes: >>If however, I turn the stack checking off (from the compiler option menu), >>the program runs fine....except that I'm really nervous about what sins >>might be hidden behind the curtains. The particular symptoms Paul describes are almost certainly really the result of stack overflow, and the fix is to determine if he really needs more stack space and if he does, then increase the size of the stack over the default 4k. >Borland Tech Support admitted to me about 6 months ago that this was >a bug in their compiler. Do *not* use the stack overflow switch for >the compiler. The bug is in TC++ 1.00 in large and huge model. Compiling with stack checking on can lead to linker errors and other randomness. It does not usually lead to bogus stack overflow error messages, and it doesn't happen in small model (I don't recall if it is in compact or medium, but if it is in one it isn't in the other), so that is not the cause of Paul's problem. The bug is fixed in version 1.01, which is available by calling Borland Customer Service at the 800 number that appears in their magazine ads. I don't want to sound commercial on the net, so I won't mention the $15 fee for shipping and materials, except to say that some people have found that if they don't ask about it when they call, *sometimes* the person taking the order forgets to ask for it :-) >Borland, are you listening? -- Sidney Markowitz Borland International (Languages R&D) [Note: I am not in Tech Support or Customer Service, and those departments are not yet hooked into our Internet connection. Any t.s. or c.s. type e-mail sent to me will be read with good intentions, but is subject to my forgetting about them when I get distracted by my next work crisis before I figure out who to pass it on to. The official channels will still work better.]