Did you look into my latest patch and try with it?

WF>>I've been working with Edin to try and track down what caused the
WF>>sudden round of crashes in the COM extension in the latest 4.3
WF>>release, and it seems that the PZVAL_UNLOCK that Stas introduced in
WF>>this commit:
WF>>
WF>>http://viewcvs.php.net/viewcvs.cgi/Zend/Attic/zend_execute.c.diff?r1=1.316.2.41&r2=1.316.2.42&hideattic=0
WF>>
WF>>fix overloaded calls not returning result, e.g.:
WF>><? new Java('foo'); ?>
WF>>
WF>>is to blame.
WF>>
WF>>If you counter-act the unlock in the COM call handler (setting is_ref
WF>>and bumping the refcount), things work "fine".  This is a hack, so I'm
WF>>hoping that you engine gurus will divine the correct fix.

I think the is_ref thing is the key, see above. I'll check with your
example on Sunday.

-- 
Stanislav Malyshev, Zend Products Engineer
[EMAIL PROTECTED]  http://www.zend.com/ +972-3-6139665 ext.115

-- 
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php

Reply via email to