On Fri, 25 Feb 2005, Herold Heiko wrote: > > Well, instead of scratching the head, how about filing a bug > > report? > > Ha :), would be nice. > I suppose that would mean calling PSS, which (if things didn't change) means > an immediate billing on your credit card (to be refunded later if there > really was a problem).
Huh? It's you who should actually charge them for doing bug discovery for them. > Anyway in this case the answer would probably be upgrade to VS.Net 2002. I don't know how that actually relates to version 6 you've mentioned, but you should just obtain a bugfix release. > But see my other email... disabling optimization as Hrvoje suggested does > work around the problem, and indeed I found some Microsoft articles > suggesting exactly that. Well, with the major version number of 6, you'd expect the product be already past its infancy, wouldn't you? Now I've heard some horror stories about C compilers crashing or producing bad code in early nineties (leading to many people avoiding any optimisation settings at all), but I've thought these times are over. Anyway, with that level of vendor (non-)support, you should really consider switching to GCC, no matter how much hassle with libraries it involves. It's just an effort to be done once and *will* pay back. Maciej
