Re: PHP has encountered an access violation...


"Jerry Stuckle" <jstucklex@xxxxxxxxxxxxx> wrote in message
news:ga30ri$dv3$2@xxxxxxxxxxxxxxxxxxxxxxxxxxxx
AqD wrote:
On Sep 8, 10:17 am, Jerry Stuckle <jstuck...@xxxxxxxxxxxxx> wrote:
AqD wrote:
On Sep 5, 8:50 pm, "Dale" <the....@xxxxxxxxxxx> wrote:
"AqD" <aquila.d...@xxxxxxxxx> wrote in message
news:749059af-db00-426b-a549-bc1c5700d1b9@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Martin wrote:
I have an intranet-only site running in Windows XPPro, IIS 5.1, PHP
5.2.5. I have not used or changed this site for several months - the
last time I worked with it, all was well.
When I tried it just now, I am getting the subject error message
(specifically: PHP has encountered an access violation at 00F76E21).
The error is NOT occurring on every page request (but it is on most
of
them) and, when I get the error, simply pressing <F5> to refresh the
page results in the page being served successfully.
Some googling around indicates that "permissions" are not set
correctly. But, if that was actually the case, a <refresh> wouldn't
work either would it? This seems to be a sporadic issue.
Any ideas as to what's going on here?
Some kind of internal bug in PHP.
and exactly HOW would you know that?!
Because the access violation is not caught and correctly reported in
PHP module, i.e. the php module crashed.
Therefore it's an internal bug.
The access violation error tells
NOTHING and you don't need to waste time on it.
hmmm...it tells you the application is trying to do something that it
is not
allowed to do. your comments seem to be the only thing wasting
anyone's
time.
Yes it is. Unless you want to spend time debugging IIS & PHP module.
Try different PHP versions or use apache to host PHP scripts. Apache
is less problemic with PHP in my experience.
well, well, well. seems like you don't really think it is 'some kind
of
internal bug in PHP' after all! now you're saying it's IIS, or any
other
webserver but apache.
if you don't have enough information to go on, don't assume so
wonderfully
and precisely what the specific problem is or what is going to solve
it!
The OP was trying to find out what the problem is. It doesn't help
him.
Even if he finds out why the problem access violation was casued, he
cannot solve it by fixing php or iis. So why waste time on things you
cannot fix?
Maybe because if no one ever took the time to find problems and report
them to Zend, problems would never get fixed.

So you would rather try to work around all of those problems caused by
an unstable product because, by your philosophy, no one should spend the
time reporting bugs.

And BTW - PHP is open source, if you hadn't known. He very well could
find and fix the problem should be be so inclined and have the time to
do so. So that's another way in which your argument is fallacious.

From the OP: "The error is NOT occurring on every page request (but it
is on most of
them) and, when I get the error, simply pressing <F5> to refresh the
page results in the page being served successfully."

PHP gives no option to dump memory or to print internal stack thrace.

If they hope people to report bugs, they should provide these things
and add some UI like "send error report" button, because most php
programmers are not C experts and it'd take too much time for them to
debug manually.


And exactly how do you expect to add a "send error report" button to a
programming language?

This has to be the most idiotic idea I've ever heard in this newsgroup!

actually, you can. you have to set up custom error handling and set a global
flag for the application that signifies whether or not the application is
running in 'debug' mode. while you can have 'report information' dumped to
your browser in php, in order to send it you'd have to take that output and
send it via some mechanism in your custom error handler. in IDE's that
support line-by-line-debugging, you would put a dialog box up from your
error handler if in 'debug' and you'd display things like the stack trace
and exception details. and, if you've worked with the window's api in
particular, you can sub-class the dialog and add a button whose click event
is a callback function...in which, you'd send the 'report'.

but then again, jerry, if you had ANY programming expericience - or, would
have learned to do less rudimentary things across your self-reported 20+
years thereof - you'd not only KNOW that it can be done and HOW TO DO IT,
you'd also see the VALUE IN IT. but, i digress...you are all
all-curtain-no-stage...all-hat-no-cattle. you've just once again proved it.


.

Quantcast