Bug #60879 [Asn]: unserialize() Does not invoke __wakeup() on object

Edit report at https://bugs.php.net/bug.php?id=60879&edit=1 ID: 60879 Updated by: johannes@php.net Reported by: thijsputman at gmail dot com Summary: unserialize() Does not invoke __wakeup() on object Status: Assigned Type: Bug Package: Class/Object related Operating System: Windows 7 PHP Version: 5.4.0RC6 -Assigned To: johannes +Assigned To: szarkos Block user comment: N Private report: N New Comment: Steve, I can't verify the report on Linux and don't see a related code-change. As I don't have a proper Windows environment at hand: From the report the user gave it seems like the compiler would do some over-optimistic optimization, can you take a look into this? Also please mind the notes on the other small issues in the configure lines. Previous Comments: ------------------------------------------------------------------------ [2012-02-08 14:02:24] thijsputman at gmail dot com The configure commands between RC7-dev (which works properly) and RC7 (which exhibits the problem) seem to differ a bit, could that be the cause? RC7 contains the following elements not contained in RC7-dev: --disable-nsapi --with-enchant=shared --disable-static-analyze --with-pgo RC7-dev contains the following not contained in RC7: --enable-object-out-dir=d:/temp/obj/nts-windows-vc9-x86 Also, there seems to be a small typo in the RC7-dev configure command: "--enable-snapshot-build --disable-zts --disable-isapi --enable-debug-pack --disable-isapi" ISAPI is disabled twice (I'm guessing the second one should be nsapi?) ------------------------------------------------------------------------ [2012-02-08 13:46:27] thijsputman at gmail dot com Just tried with RC7 (VC9 x86 Non Thread Safe - 2012-Feb-06 23:40:37) and the problem has reappeared... ------------------------------------------------------------------------ [2012-02-06 13:44:29] yoozer at gmail dot com I've just tested the official release of RC7; it still exhibits this issue with exactly the same testcase. ------------------------------------------------------------------------ [2012-01-26 11:33:25] johannes@php.net So let's assume this was fixed. I can't see a relevant change for this, though. There will be another RC soon, an you check that, too, to be safe? Thanks :-) ------------------------------------------------------------------------ [2012-01-26 10:56:17] thijsputman at gmail dot com Just tried with revision 322785 and it indeed works as expected. To assert my sanity I re-downloaded 5.4.0RC6 (VC9 x86 Non Thread Safe, 2012-Jan-19 23:40:07) from the QA website and in that release the problem does exist. ------------------------------------------------------------------------ The remainder of the comments for this report are too long. To view the rest of the comments, please view the bug report online at https://bugs.php.net/bug.php?id=60879 -- Edit this bug report at https://bugs.php.net/bug.php?id=60879&edit=1