Hi!
> Just to put things in perspective, if opcode caches with extended info
> make it into the opcode cache - it's a bad thing. So it's actually
Yeah, we should definitely check for extended info and shortcut
compile_file immediately if that is there. Should be an easy patch, I'll
try to do pull tonight. If that's the problem behind Rasmus' crash, it's
easy to fix.
> expected that debuggers and opcode caches would have to be aware of
> one another, but at a pretty minimal level. The load order solves it
> most probably because then it means Xdebug kicks in first, and
> wouldn't pass op arrays to O+. That's guesswork though, we'd have to
> ensure that and ideally also have a mechanism to enforce it.
Yeah, that is what I was worried about if there's no other problems
deeper than the extended info one and how to handle it in an elegant
fashion without hardcoding checks for specific names.
--
Stanislav Malyshev, Software Architect
SugarCRM: http://www.sugarcrm.com/
(408)454-6900 ext. 227