: [PHP-DEV] Segfault in HEAD with PHPUnit2
When I run PHPUnit2's own testsuite with a Release_TS build of
PHP 5.1.0-CVS I get a segfault (no backtrace since no symbols) on
shutdown.
When I run the same PHP sources with a Debug_TS build of PHP 5.1.0-CVS I
do not get a segfault but messages
When I run PHPUnit2's own testsuite with a Release_TS build of
PHP 5.1.0-CVS I get a segfault (no backtrace since no symbols) on
shutdown.
When I run the same PHP sources with a Debug_TS build of PHP 5.1.0-CVS I
do not get a segfault but messages like this
[Sat Apr 23 10:31:14 2005]
Sterling,
It's a stack overflow caused by an infinite loop in function calls (i.e.
not while/for loop).
Andi
At 10:17 AM 3/31/2004 -0800, Sterling Hughes wrote:
php5 shouldn't crash _at all_ within an infinite loop because we aren't in
one big execution loop.
-sterling
On Mar 30, 2004, at
On Thu, 01 Apr 2004 10:36:43 +0200
Andi Gutmans [EMAIL PROTECTED] wrote:
Sterling,
It's a stack overflow caused by an infinite loop in function calls (i.e.
not while/for loop).
So, it's ok and won't be fixed ?
---
WBR,
Antony Dovgal aka tony2001
[EMAIL PROTECTED] || [EMAIL PROTECTED]
--
On Thu, 1 Apr 2004, Antony Dovgal wrote:
On Thu, 01 Apr 2004 10:36:43 +0200
Andi Gutmans [EMAIL PROTECTED] wrote:
Sterling,
It's a stack overflow caused by an infinite loop in function calls (i.e.
not while/for loop).
So, it's ok and won't be fixed ?
Exactly (though adding in a hard
At 12:41 PM 4/1/2004 +0400, Antony Dovgal wrote:
On Thu, 01 Apr 2004 10:36:43 +0200
Andi Gutmans [EMAIL PROTECTED] wrote:
Sterling,
It's a stack overflow caused by an infinite loop in function calls (i.e.
not while/for loop).
So, it's ok and won't be fixed ?
This has been discussed many times.
php5 shouldn't crash _at all_ within an infinite loop because we aren't
in one big execution loop.
-sterling
On Mar 30, 2004, at 11:27 PM, Derick Rethans wrote:
On Wed, 31 Mar 2004, Antony Dovgal wrote:
Hi all!
This small script:
?
class test {
var $a = false;
var $x = false;
On Mar 31, 2004, at 1:17 PM, Sterling Hughes wrote:
php5 shouldn't crash _at all_ within an infinite loop because we
aren't in one big execution loop.
Why shouldn't this crash eventually? You still have to account for all
the callers stacks.
George
--
PHP Internals - PHP Runtime Development
Hi all!
This small script:
?
class test {
var $a = false;
var $x = false;
function getA() {
if (!$this-x) { // yep, I know, it's infinite loop
$this-foo();
}
return $this-a;
}
On Wed, 31 Mar 2004, Antony Dovgal wrote:
Hi all!
This small script:
?
class test {
var $a = false;
var $x = false;
function getA() {
if (!$this-x) { // yep, I know, it's infinite loop
PHP always crashes on infinite loops as you might be aware off.
On Wed, 31 Mar 2004 09:27:42 +0200 (CEST)
Derick Rethans [EMAIL PROTECTED] wrote:
On Wed, 31 Mar 2004, Antony Dovgal wrote:
Hi all!
This small script:
?
class test {
var $a = false;
var $x = false;
function getA() {
if (!$this-x) { // yep, I know,
On Wed, 31 Mar 2004, Antony Dovgal wrote:
PHP always crashes on infinite loops as you might be aware off. You'll
have to live with it.
And there is no workarounds at all?
(BTW, same results with PHP_4_3..)
Just don't make infinite loops? :)
Derick
--
PHP Internals - PHP Runtime
Hi all!
#0 0x8038 in ?? ()
#1 0x40331677 in zend_isset_isempty_prop_obj_handler (execute_data=0x4136becc,
opline=0x4136becc, op_array=0x4136becc)
at /home/tony/CVS/php-src/Zend/zend_execute.c:3995
#2 0x4032ab1a in execute (op_array=0x80ffaf4) at
This should be fixed now. Thanks for the short reproducing script.
Andi
At 11:41 PM 2/26/2004 +0100, Stefan Walk wrote:
Hi, after a cvs update i get a segfault with this script:
?php
class test
{
function __destruct() {
$this-foo = false;
}
public function start() {
throw new
On Thu, 2004-02-26 at 23:41, Stefan Walk wrote:
Hi, after a cvs update i get a segfault with this script:
[...]
This sourcecode (which is the same except that there is no code in the
destructor) prints out:
Fatal error: Exception thrown without a stack frame in Unknown on line 0
-- snip --
zend_fetch_obj_w_handler(_zend_execute_data * 0x0012f488, _zend_op *
0x00c68660, _zend_op_array * 0x00c67588, void * * * 0x009742d0) line 2044
+ 12 bytes
execute(_zend_op_array * 0x00c67588, void * * * 0x009742d0) line 1339 + 23
bytes
zend_do_fcall_common_helper(_zend_execute_data * 0x0012f610,
Hi, after a cvs update i get a segfault with this script:
?php
class test
{
function __destruct() {
$this-foo = false;
}
public function start() {
throw new Exception();
}
}
$test = new test();
$test-start();
?
Backtrace:
#0 0x in ?? ()
#1 0x081656a2 in execute
Fixed.
At 05:42 PM 12/6/2003 +0100, Andrey Hristov wrote:
Hi,
the following script segfaults when HEAD is used (no problem with PHP_4_3).
?php
$s = FUBAR;
$s[0][] = 1;
?
Here is a session that shows the script and the error spotted by valgrind.
[session]
bash-2.05b$ cat soffset.php
?php
$s =
Hi,
When I try to run phpDocumentor with HEAD in win32/apache 1.3 checked
out a few minutes ago, I get a segfault, here's a stack trace grabbed
from VS:
php5ts_debug.dll!execute(_zend_op_array * op_array=0x0109f020, void * *
* tsrm_ls=0x010925d8) Line 1270 + 0x15 C
Hi Greg,
Do you have a short script to reproduce it or at least the last working
line in phpdocumentor?
I'm working a bit in ZE2 these days for a project, should be a good
exercise, aka a 2nd bugfixe :)
hth
pierre
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit:
On Wed, 24 Sep 2003 20:18:28 +0100 (BST)
Wez Furlong [EMAIL PROTECTED] wrote:
The memory manager will deliberately segfault if an allocation fails in a debug
build.
Having said that, your patch seems ok anyway.
hmmm.. patch is ok, but still not commited =\
---
WBR,
Antony Dovgal aka
Hi, all!
This script (you need to compile PHP with --enable-memory-limit first):
?
ini_set(memory_limit,0);
phpinfo();
?
produces for me segfault with last HEAD and PHP_4_3 branch.
Backtrace:
Program received signal SIGSEGV, Segmentation fault.
_efree (ptr=0x0) at
The memory manager will deliberately segfault if an allocation fails in a debug
build.
Having said that, your patch seems ok anyway.
--Wez.
On Wed, 24 Sep 2003, Antony Dovgal wrote:
Hi, all!
This script (you need to compile PHP with --enable-memory-limit first):
?
ini_set(memory_limit,0);
23 matches
Mail list logo
