Re: PHP 4.0 Bug #4939: Unhandled ExceptioninPHP4TS.DLL - Access Violation
| From: | Fred Merritt | Date: | Sat, 10 Jun 2000 21:42:27 +0000 |
| Subject: | Re: PHP 4.0 Bug #4939: Unhandled ExceptioninPHP4TS.DLL - Access Violation | ||
| References: | 1 2 3 | Groups: | php.dev |
| Request: | Send a blank email to php-dev+get-21054@lists.php.net to get a copy of this message | ||
Andi,
the plot thickens.
In order to eliminate apache, I have been running from the command line.
>From the command line, if I run the debug_ts version, then I get the html
out, as expected.
If I run the release_ts version, then the script fails, with unable
to find file. Running from the command line also enabled me to start
from the VC debugger, and step through the code, for both the release and
debug versions. After a lot of thrashing about, I eventually found
that the code seems to fail very early on in cgi_main.c
If I set a break on line 359, in cgi_main, and single step through the
sequence of executed statements in the debug version this is 360, 364,
365, 366, 367, 368(which seems correct).
If I do the same in the release version, the code steps directly from
359 to 368. Also if I try to inspect any of the missed variables,
they are not available in the release version, however they appear in the
debug version.
I did a rebuild all, and got exactly the same failure. I recompiled
cgi_main.c, with the listing options on, as I was suspecting that maybe
the pre-processor had screwed up, but the listing had all the right statements
in it. I'm a bit suspicious of the debugger, but I can't really see
anything, I can directly pin on the debugger. When I compiled the
original release binaries, I was failing on the same address, as the PHP
released binaries. I don't know if any of you experienced C programmers
have seen this kind of behaviour before, but I for the moment am mystified,
but not yet giving up.
Best regards. . . Fred