#34024 [Opn->Fbk]: PHP has encountered an Access Violation at 019382DF (ISAPI)

ID: 34024 Updated by: tony2001@php.net Reported By: andrey at cherezov dot koenig dot su -Status: Open +Status: Feedback Bug Type: Scripting Engine problem Operating System: Windows 2003 PHP Version: 5CVS-2005-08-07 (dev) New Comment: So it comes that you can provide some info in addition to this address, right? I doubt I can use it on Linux to get a backtrace or something useful, so please do provide more info yourself. >If you're not interested in ISAPI, just say it. Yes, we are. But in most cases users do not understand that just stating that something is wrong doesn't help. If you can provide more info about it - please do so. >I will switch back to CGI and forget about these bugs. This way you won't get a stable ISAPI module ever. Previous Comments: ------------------------------------------------------------------------ [2005-08-07 10:53:25] andrey at cherezov dot koenig dot su 1. The address of exception is not meaningless. When exception happens in my own programs I can easily locate the faulting function because the exception record structure have all required pointers for it, and the call stack is also available to dump at exception moment. Learn from Microsoft ;) 2. And I offered a way to 'catch' any info related to this exception by turn on runtime tracing: I can run the debug version of php5isapi.dll, if you provide one, and I will send you its log when next exception occured. It is obviously and pretty easy to implement. If you'll continue to wave aside such 'unreproducible' issues, you'll never release the stable enough ISAPI module. If you're not interested in ISAPI, just say it. I will switch back to CGI and forget about these bugs. Thank you for help, Good luck, ------------------------------------------------------------------------ [2005-08-07 10:25:32] tony2001@php.net So how do you expect us to fix an issue that is not reproducible and all you can provide about it is a meaningless memory address? ------------------------------------------------------------------------ [2005-08-07 10:14:13] andrey at cherezov dot koenig dot su Tony, this is a random multithreading issue, it is impossible to make 'reproduce script' for this kind of bugs. It requires reproducing the same threads and memory state. ------------------------------------------------------------------------ [2005-08-07 09:43:51] tony2001@php.net >This address 019382DF not gives a pointer to a problem function? It gives nothing. Please generate a backtrace and provide a short but complete reproduce script. ------------------------------------------------------------------------ [2005-08-07 04:46:44] andrey at cherezov dot koenig dot su I can't use Apache2 on this site - there a lot of virtual hosts on this server depending of exact configuration, not supported by Apache at all. This address 019382DF not gives a pointer to a problem function? I can run on the my server any debug PHP version and send its trace log (or how you explore such bugs) to you, if you need. Any PHP variant, but not Apache, sorry. ------------------------------------------------------------------------ The remainder of the comments for this report are too long. To view the rest of the comments, please view the bug report online at http://bugs.php.net/34024 -- Edit this bug report at http://bugs.php.net/?id=34024&edit=1