Hi Rasmus, Sorry but no for this one. I've been emailing with Andi for a bit, and I'm trawling through with gdb. It's very bizarre, and looks like just a symptom of some general memory corruption at the moment. I'm not sure that array_reduce is itself to blame. Any number of minor changes stop the problem from happening - such as the call stack depth, what the function to array_reduce does, and so on. I've eliminated a certain amount of complexity, and up to a point, as long as I keep the call stack depth the same with dummy functions then I can keep the crash happening, but I've reached a point where if I further simplify then things don't fail. I'm going to see if I can further simplify and will give an update if I have anything more tangible to add on this. Thanks for your email, Best regards, Nick -- PHP Development Mailing List <http://www.php.net/> To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] To contact the list administrators, e-mail: [EMAIL PROTECTED]
