Re: Re: 4.0.2, another showstopper

At 10:12 28/08/2000, André Langhorst wrote:

Your machine is seriously broken Andre :) Seriously, something's broken in your build. Badly. You cured one of the symptoms and not the disease with that C-runtime exclude you added (stuff that got built against the release C runtime got linked with the debug C runtime - it's not *supposed* to work!). Needless to say, neither of the above crashes with the latest CVS on my box(es).

hey, I forgot to mention, my machine is cured already! I´ve found that the two resolv.lib´s I used were the same, now everything is fine, debug, release build, everything... did you *try* if include('non-existent') crashes?

Yes, it doesn't. It happily prints out <b>Warning</b>: Failed opening 'non existent file' for inclusion (include_path='') in <b>test.php</b> on line <b>2</b><br> (ok, I lied, I didn't test include('non-existent'), I tested include('non existent file') :)

My builds are allright now (and release builds were right the whole time, it was just that I built bindlib many month ago and there made the fault to use the same lib for both builds so my machine is ok., I´ve got a clean tree and everything is wonderful, but these crashes... if you don´t get any crash I´ll prepare a backtrace

Something's still broken about your build if you're getting these all-too-obvious crashes. It's not 100.0% certain, but it's much more likely than a bug in the code that's been solid for quite a while. Please prepare a backtrace. By the way, there's no need for BugTrapper for a simple backtrace; Run the program in the VC debugger, and when it crashes, go to View->Debug Windows->Call Stack. Select all of the text, ^C, and paste it to your Email program. Zeev -- Zeev Suraski <zeev@zend.com> http://www.zend.com/