Re: Segfaults in Zend

Derick Rethans wrote:

On Mon, 7 Oct 2002, Jan Schneider wrote:

In another script the segfaults occur in another place. It's hard to trap it down cause it happens during inside a foreach loop. It doesn't happen after the first loop but at any of the subsequent loops. Inside this loop happens - beside a call to imap_utf7_decode() that wasn't called in the the first script - only some assignments and string and array functions. So I guess this actually has something to do with the engine.

If you are on linux, you can try valgrind (http://developer.kde.org/~sewardj/) like this: (first stop httpd) valgrind --gdb-attach /path/to/httpd -X then request your script and check the valgrind console window. It asks to attach when something goes wrong, press "Y" and then "bt" from gdb. This should give a good understanding where it goes wrong. I'd like to but I get an "unhandled syscall: 197" though I don't even have such a call in unistd.h. :-(