Tarjei Huse wrote: > > Any chance of getting a stack trace? If it's in multiple update functions, it > > must be somewhere in midgard-lib. > > Program received signal SIGSEGV, Segmentation fault. > 0x40134a8d in free () from /lib/libc.so.6 > (gdb) backtrace > #0 0x40134a8d in free () from /lib/libc.so.6 > #1 0x404296db in _efree () from /usr/lib/apache/1.3/libphp4.so > #2 0x40441905 in _zval_dtor () from /usr/lib/apache/1.3/libphp4.so > #3 0x4043a159 in _zval_ptr_dtor () from /usr/lib/apache/1.3/libphp4.so > #4 0x4044757e in zend_hash_destroy () from /usr/lib/apache/1.3/libphp4.so > #5 0x4044194b in _zval_dtor () from /usr/lib/apache/1.3/libphp4.so > #6 0x4043a159 in _zval_ptr_dtor () from /usr/lib/apache/1.3/libphp4.so > #7 0x40438040 in execute () from /usr/lib/apache/1.3/libphp4.so > #8 0x40434df1 in execute () from /usr/lib/apache/1.3/libphp4.so > #9 0x42931d04 in zif_mgd_variable () from /usr/lib/php4/20010901/midgard.so > #10 0x4293219d in zif_mgd_eval () from /usr/lib/php4/20010901/midgard.so > #11 0x404347d9 in execute () from /usr/lib/apache/1.3/libphp4.so > #12 0x42931d04 in zif_mgd_variable () from /usr/lib/php4/20010901/midgard.so > #13 0x4293219d in zif_mgd_eval () from /usr/lib/php4/20010901/midgard.so > #14 0x404347d9 in execute () from /usr/lib/apache/1.3/libphp4.so
... etc etc Weird... I don't know how this would be specific to $obj->update. For some reason it's stuck in an eval loop. But I'm using nadmin at Envida and at home and I've never seen anything like this, Maybe a bit forward to ask, but could you try your code on an mmp install? I have a feeling there's an eval accidently being changed into mgd_eval (which is how non-mmp handled things), and if that's the issue it should be gone with mmp. Emile --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
