This also happens in 5.1.0RC1, btw:
Breakpoint 1, zend_throw_exception_internal (exception=0xa19baa4) at
/root/webserver_software_tmp_fastcgi_apache2/php-5.1.0RC1/Zend/zend_exceptions.c:39
39 if (exception != NULL) {
(gdb) bt
#0 zend_throw_exception_internal (exception=0xa19baa4) at
On 8/30/05, Marcus Boerger <[EMAIL PROTECTED]> wrote:
> in 15 you see that all parameters are bork!
If that is true, then 10, 15, and 24 (all call_user_function_ex) are
borked. 24 would be the earliest. Maybe something is being cleaned up
at the start of shutdown but before the user shutdown funct
This was with:
/usr/bin/valgrind --tool=memcheck --leak-check=yes -v --trace-children=yes
And it didn't seem to add anything while the errorlog was being written.
# more log.pid17870
==17870== Memcheck, a memory error detector for x86-linux.
==17870== Copyright (C) 2002-2004, and GNU GPL'd, by
Yea, I noticed that too...
#!/bin/bash
export PHPRC
export PHP_FCGI_CHILDREN
exec /usr/bin/valgrind --tool=memcheck --trace-children=yes \
--log-file=/usr/local/apache2/fastcgi-bin/log
/usr/local/apache2/fastcgi-bin/php505.fcgi $@
This one works. :)
However... it didn't seem to find much.
--
PH
Hello steve,
Tuesday, August 30, 2005, 11:32:33 PM, you wrote:
> :)
> Can valgrind attach to a process like gdb? I somehow doubt it... In
> that case, I must admit, I've never used valgrind before. How can I
> set up valgrind to check a fast-cgi process?
> I tried changing the php5.fcgi file to
:)
Can valgrind attach to a process like gdb? I somehow doubt it... In
that case, I must admit, I've never used valgrind before. How can I
set up valgrind to check a fast-cgi process?
I tried changing the php5.fcgi file to php505.fcgi and created this as
php5.fcgi:
#/bin/bash
/usr/bin/valgrind -
