Bug #63096 [Fbk]: Crash when run cli script

From: Date: Mon, 17 Sep 2012 13:13:17 +0000
Subject: Bug #63096 [Fbk]: Crash when run cli script
References: 1  Groups: php.bugs 
Request: Send a blank email to php-bugs+get-173497@lists.php.net to get a copy of this message
Edit report at https://bugs.php.net/bug.php?id=63096&edit=1 ID: 63096 Updated by: pajoye@php.net Reported by: pracanowo at gmail dot com Summary: Crash when run cli script Status: Feedback Type: Bug Package: *General Issues Operating System: win xp sp3 PHP Version: 5.4.7 Block user comment: N Private report: N New Comment: ok, as you mentioned that you pcre, I seriously hope that you are not parsing HTML using pcre. That's the best to end in a stack overflow crash with PCRE. Use tidy or DOM instead. Alternatively you can increase the stack size of the php.exe (using editbin.exe). Previous Comments: ------------------------------------------------------------------------ [2012-09-17 11:45:04] pracanowo at gmail dot com ok i find it str_get_html() from "PHP Simple HTML DOM Parser". Now i need only save bugy html ------------------------------------------------------------------------ [2012-09-17 10:28:32] pajoye@php.net First of all, please post a clean backtrace. See https://bugs.php.net/bugs-generating-backtrace-win32.php ------------------------------------------------------------------------ [2012-09-16 01:31:01] reeze@php.net Could you please try to get a reproducible test script ? if possible it would be much easier to spot. ------------------------------------------------------------------------ [2012-09-15 20:48:36] pracanowo at gmail dot com Error are somtimes random, script parse lot of data [ so i think is preg ], on Monday i will be able to reproduce error, now all sessio that my script need handle are finish. I need also create some markers in my code. Now i install Xdebug. I remember in 5.3 whose the same now i update to 5.4.7 ------------------------------------------------------------------------ [2012-09-15 19:32:54] felipe@php.net Thank you for this bug report. To properly diagnose the problem, we need a short but complete example script to be able to reproduce this bug ourselves. A proper reproducing script starts with <?php and ends with ?>, is max. 10-20 lines long and does not require any external resources such as databases, etc. If the script requires a database to demonstrate the issue, please make sure it creates all necessary tables, stored procedures etc. Please avoid embedding huge scripts into the report. ------------------------------------------------------------------------ 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=63096 -- Edit this bug report at https://bugs.php.net/bug.php?id=63096&edit=1

« previous php.bugs (#173497) next »