Edin Kadribasic wrote:
> You can configure PHP with --enable-debug-pack which will compile
> release version of the binaries with external debug symbols.
Thank you for this information. The issue I was experiencing has been
fixed by Marcus in CVS already.
--
Sebastian Bergmann
Hi Sebastian,
You can configure PHP with --enable-debug-pack which will compile release
version of the binaries with external debug symbols.
Edin
- Original Message -
From: "Sebastian Bergmann" <[EMAIL PROTECTED]>
To:
Sent: Saturday, April 23, 2005 10:36 AM
Subject: [P
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] Scri
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 t
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 ad
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]
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 11
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 M
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 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 D
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
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 o
Hi all!
This small script:
x) { // yep, I know, it's infinite loop
$this->foo();
}
return $this->a;
}
function foo() {
return $this->getA();
}
}
$test = new test;
$test->getA();
?>
produces segfault
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
/home/tony/CVS/php-src/Zend/zend_execut
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:
foo = false;
}
public function start() {
throw new Exception();
}
}
$test = new test();
$test->start();
?
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 --
sta
Hi, after a cvs update i get a segfault with this script:
foo = false;
}
public function start() {
throw new Exception();
}
}
$test = new test();
$test->start();
?>
Backtrace:
#0 0x in ?? ()
#1 0x081656a2 in execute (op_array=0x40206284) at
/home/et/cvs.php.net/php-src/Z
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, _ze
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).
Here is a session that shows the script and the error spotted by valgrind.
[session]
bash-2.05b$ cat soffset.php
bash-2.05b$ valgrind ./php soffset.php
==4985
Please add this as one regression test..there are never too many
of these. (If it doesn't already exist)
--Jani
On Sat, 6 Dec 2003, Andrey Hristov wrote:
>Hi,
>the following script segfaults when HEAD is used (no problem with PHP_4_3).
>$s = "FUBAR";
>$s[0][] = 1;
>?>
>
>Here is
Hi,
the following script segfaults when HEAD is used (no problem with PHP_4_3).
Here is a session that shows the script and the error spotted by valgrind.
[session]
bash-2.05b$ cat soffset.php
$s = "FUBAR";
$s[0][] = 1;
?>
bash-2.05b$ valgrind ./php soffset.php
==4985== Memcheck, a.k.a. Valgrind,
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 t
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",
Hi, all!
This script (you need to compile PHP with --enable-memory-limit first):
produces for me segfault with last HEAD and PHP_4_3 branch.
Backtrace:
Program received signal SIGSEGV, Segmentation fault.
_efree (ptr=0x0) at /root/CVS/php-src/Zend/zend_alloc.c:257
257 CALCULATE_REAL
24 matches
Mail list logo
