Re: [PHP-DEV] segfault with ze2/php5-cvs

On Fri, 2003-03-21 at 15:12, Joey Smith wrote: > Very nice. > > What about: > >class person { > var $name; > } > > $start = new person; > $start->name = 'Eve'; > $new = $start->__clone(); > ?> > > Does it come back with 'Call to a member function on

Re: [PHP-DEV] segfault with ze2/php5-cvs

Very nice. What about: name = 'Eve'; $new = $start->__clone(); ?> Does it come back with 'Call to a member function on a non-object'? On Fri, Mar 21, 2003 at 02:47:06PM -0500, Sterling Hughes wrote: > class sheep { > var $name; > } > > $start = new sheep; > $start->name = "Dolly"

Re: [PHP-DEV] Segfault with latest CVS

Derick Rethans wrote: > uhm, this will be fixed ... some time :) Zeev fixed it. -- Sebastian Bergmann http://sebastian-bergmann.de/ http://phpOpenTracker.de/ Did I help you? Consider a gift: http://wishlist.sebastian-bergmann.de/ -- PHP Development Mailing List

Re: [PHP-DEV] Segfault with latest CVS

On Wed, 12 Mar 2003, Martin Jansen wrote: > On Tue Mar 11, 2003 at 10:5232PM +0100, Sebastian Bergmann wrote: > > Martin Jansen wrote: > > > > > > > Most likely this will be caused by > > > > 856 $this->$key = &$arr[$key]; > > > > as variable member access causes a segfault in the comp

Re: [PHP-DEV] Segfault with latest CVS

On Tue Mar 11, 2003 at 10:5232PM +0100, Sebastian Bergmann wrote: > Martin Jansen wrote: > > > > Most likely this will be caused by > > 856 $this->$key = &$arr[$key]; > > as variable member access causes a segfault in the compiler. Will this be fixed or has there been a decision to lea

Re: [PHP-DEV] Segfault

Fixed! Thanks, Zeev At 18:17 11/03/2003, Andrei Zmievski wrote: With the latest ZE2: class Bar { function boo() { ::zoo(); } } Bar::boo(); ?> -Andrei http://www.gravitonic.com/ "The day Microsoft makes something that doesn't suck, is p

Re: [PHP-DEV] Segfault with latest CVS

Martin Jansen wrote: > Most likely this will be caused by 856 $this->$key = &$arr[$key]; as variable member access causes a segfault in the compiler. -- Sebastian Bergmann http://sebastian-bergmann.de/ http://phpOpenTracker.de/ Did I help you? Consider a gift: h

Re: [PHP-DEV] segfault in latest CVS

On Thu, 12 Dec 2002, Kai Schröder wrote: > I got a segmentation fault during configure php (today cvs) on Linux (SuSE > 7.3, Kernel 2.4.20). Last line was "checking getpwnam... no". Do you still have this problem? Derick -- -

Re: [PHP-DEV] Segfault with current CVS.

After some further investigation I found out that it was bcmath causing this. Here's my config.nice: #! /bin/sh # # Created by configure './configure' \ '--disable-all' \ '--prefix=/usr/local/www/php4' \ '--with-apxs2=/usr/local/www/httpd2test/bin/apxs' \ '--enable-debug' \ '--enable-experimenta

Re: [PHP-DEV] Segfault in implode()

On Sun, Oct 06, 2002 at 12:10:17PM +0200, Martin Jansen wrote: > FYI: Yesterdays snapshot segfaults with the following line of code: > > $foo = implode("", array()); > ?> Fixed in CVS, thanks for the report. Sander -- PHP Development Mailing List

Re: [PHP-DEV] Segfault in implode()

Hi, On Sun, Oct 06, 2002 at 12:10:17PM +0200, Martin Jansen wrote: > FYI: Yesterdays snapshot segfaults with the following line of code: > > $foo = implode("", array()); > ?> I cannot reproduce this with current HEAD on FreeBSD, can you give more information about your bu

Re: [PHP-DEV] Segfault in 4.2.3RC2

The problem described here occurs both in 4.2.3RC2 & 4.3.0-dev. The attached patch is against 4.3.0-dev (HEAD) and as far as my testing shows addresses the problem. The source of the segfault is a buffer overflow that results when estimated number of times the separator will be inserted is les

Re: [PHP-DEV] Segfault in 4.2.3RC2

On Wed Sep 04, 2002 at 09:3027PM +0200, Martin Jansen wrote: > Obviously PHP 4.2.3RC2 segfaults when using wordwrap() with the > following configure options: If it helps you, attached you'll find the backtrace of the crash. -- - Martin Martin Jansen

Re: [PHP-DEV] Segfault in 4.2.3RC2

Vergoz Michael \ <[EMAIL PROTECTED]> wrote: > me too.. Maybe your mail/news reader has a problem with the trailing dot, maybe Martin fixed it now. works for me, and I can see the segfault with 4.2.3RC2, configured only with --enable-debug -

Re: [PHP-DEV] Segfault in 4.2.3RC2

On Mit Sep 04, 2002 at 09:3724 +0200, [EMAIL PROTECTED] wrote: > On Wed, 4 Sep 2002, Martin Jansen wrote: > > > The script to reproduce the segfault can be found at > > http://www.martinjansen.com/php/segfault-4.2.3RC2.txt. If you need > > more information (backtrace etc.), just ask. > > That li

Re: [PHP-DEV] Segfault in 4.2.3RC2

me too.. - Original Message - From: <[EMAIL PROTECTED]> To: "Martin Jansen" <[EMAIL PROTECTED]> Cc: <[EMAIL PROTECTED]> Sent: Wednesday, September 04, 2002 9:37 PM Subject: Re: [PHP-DEV] Segfault in 4.2.3RC2 > On Wed, 4 Sep 2002, Martin Jansen wrote: &g

Re: [PHP-DEV] Segfault in 4.2.3RC2

On Wed, 4 Sep 2002, Martin Jansen wrote: > The script to reproduce the segfault can be found at > http://www.martinjansen.com/php/segfault-4.2.3RC2.txt. If you need > more information (backtrace etc.), just ask. That link gives a four oh four to me... Derick ---

Re: [PHP-DEV] segfault on adding empty heredoc to string

On Mon, Sep 02, 2002 at 02:22:12AM +0300, Zeev Suraski wrote: | Mark them as critical and they'll get some attention :) | | Is this bug new to the latest CVS or does it occur with 4.2? I gave the code snippet a try here with a CGI SAPI version of PHP 4.2.2. I wasn't able to reproduce the crash:

Re: [PHP-DEV] Segfault in ob_*() callback

This is known issue for a long time. Sebastian Bergmann wrote: > Marcus Börger wrote: > >>The problem here again is that in ob handlers no ob_xxx() function can >>be called. > *SNIP* > > It'd be okay IMHO to prohibit ob_*() calls inside a handler. > There are functions like this. i.e. arra

Re: [PHP-DEV] segfault on adding empty heredoc to string

Mark them as critical and they'll get some attention :) Is this bug new to the latest CVS or does it occur with 4.2? At 01:10 02/09/2002, Jani Taskinen wrote: > > Crashes with latest CVS HEAD here too: > >0x828b505 in _zval_dtor (zvalue=0xbfffd540, __zend_filename=0x8376000 >"/usr/src/web/ph

Re: [PHP-DEV] segfault on adding empty heredoc to string

Crashes with latest CVS HEAD here too: 0x828b505 in _zval_dtor (zvalue=0xbfffd540, __zend_filename=0x8376000 "/usr/src/web/php/php4/Zend/zend_operators.c", __zend_lineno=1057) at /usr/src/web/php/php4/Zend/zend_variables.c:43 43 CHECK_ZVAL_STRING_REL(zval

Re: [PHP-DEV] segfault on adding empty heredoc to string

On Sun, 2002-09-01 at 19:50, Lukas Schroeder wrote: > hi, > > i can crash my php here by using these lines: Nope, works fine: --- thekid@friebes:~ > cat | php -q thekid@friebes:~ > php -v 4.2.1 thekid@friebes:~ > uname -a FreeBSD

RE: [PHP-DEV] segfault on adding empty heredoc to string

No problems with 4.2.2 as apache-1.3.26 dso on RH-7.2 Regards Mike Robinson -Original Message- From: Lukas Schroeder [mailto:[EMAIL PROTECTED]] Sent: Sunday, September 01, 2002 1:50 PM To: [EMAIL PROTECTED] Subject: [PHP-DEV] segfault on adding empty heredoc to string hi, i can cras

Re: [PHP-DEV] segfault on adding empty heredoc to string

No problems on win32 , php-430-dev cli.ZE2. Best regards Andrey Hristov - Original Message - From: "Lukas Schroeder" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Sunday, September 01, 2002 8:50 PM Subject: [PHP-DEV] segfault on adding empty heredoc to string > hi, > > i can crash

Re: [PHP-DEV] segfault on adding empty heredoc to string

Hey, I can reproduce this crash: Program received signal SIGSEGV, Segmentation fault. 0x081f8ddf in _zval_dtor (zvalue=0xbfffd3f0, __zend_filename=0x8272220 "/dat/dev/php/php-4.3.0dev/Zend/zend_operators.c", __zend_lineno=1057) at /dat/dev/php/php-4.3.0dev/Zend/zend_variables.c:43 43

Re: [PHP-DEV] Segfault in ob_*() callback

At 18:02 01.09.2002, Sebastian Bergmann wrote: >Marcus Börger wrote: > > The problem here again is that in ob handlers no ob_xxx() function can > > be called. > > FYI: I know that I shouldn't do that, but I tried > > class Test { > function Test() { > ob_start(array($this,

Re: [PHP-DEV] Segfault in ob_*() callback

Marcus Börger wrote: > The problem here again is that in ob handlers no ob_xxx() function can > be called. FYI: I know that I shouldn't do that, but I tried out of curiosity, while trying to get Cache_Lite working with XML_Transformer. It'd be okay IMHO to prohibit ob_*() calls in

Re: [PHP-DEV] Segfault in ob_*() callback

At 17:10 01.09.2002, Zeev Suraski wrote: >At 17:51 01/09/2002, Marcus Börger wrote: >>At 15:25 01.09.2002, Zeev Suraski wrote: >>>At 16:10 01/09/2002, Marcus Börger wrote: The problem is that in function PHPAPI void php_end_ob_buffer(zend_bool send_buffer, zend_bool just_flush TSRMLS_

Re: [PHP-DEV] Segfault in ob_*() callback

At 17:51 01/09/2002, Marcus Börger wrote: >At 15:25 01.09.2002, Zeev Suraski wrote: >>At 16:10 01/09/2002, Marcus Börger wrote: >>>The problem is that in function >>>PHPAPI void php_end_ob_buffer(zend_bool send_buffer, zend_bool >>>just_flush TSRMLS_DC) >>> >>>the user function is called wether o

Re: [PHP-DEV] Segfault in ob_*() callback

At 15:25 01.09.2002, Zeev Suraski wrote: >At 16:10 01/09/2002, Marcus Börger wrote: >>The problem is that in function >>PHPAPI void php_end_ob_buffer(zend_bool send_buffer, zend_bool just_flush >>TSRMLS_DC) >> >>the user function is called wether or not send_buffer is zero. (Zero >>means flush >

Re: [PHP-DEV] Segfault in ob_*() callback

At 16:10 01/09/2002, Marcus Börger wrote: >The problem is that in function >PHPAPI void php_end_ob_buffer(zend_bool send_buffer, zend_bool just_flush >TSRMLS_DC) > >the user function is called wether or not send_buffer is zero. (Zero means >flush >here and means the function must not be called,

Re: [PHP-DEV] Segfault in ob_*() callback

At 15:06 01.09.2002, Sebastian Bergmann wrote: >Marcus Börger wrote: > > Ever tried this in earlier version of PHP? I guess not! > > I tested it with PHP 4.2.3-RC1, and it's broken there, too. > > I did not claim that you broke this one, Marcus, so why the harsh > tone? Because you rev

Re: [PHP-DEV] Segfault in ob_*() callback

Marcus Börger wrote: > Ever tried this in earlier version of PHP? I guess not! I tested it with PHP 4.2.3-RC1, and it's broken there, too. I did not claim that you broke this one, Marcus, so why the harsh tone? -- Sebastian Bergmann http://sebastian-bergmann.de/ h

Re: [PHP-DEV] Segfault in ob_*() callback

At 10:10 31.08.2002, Sebastian Bergmann wrote: > Reproducing script: > > class Test { > function Test() { > ob_start(array($this, 'transform')); > } > > function transform($buffer) { > ob_end_clean(); > return $buffer; > } > } > >

Re: [PHP-DEV] segfault in recent code

On 2002-08-01 02:28:26, Rasmus Lerdorf wrote: > That fixed part of it, there is still another segfault in there somewhere. Maybe it has to do with the silly strncasecmp error I made (and just committed a fix to SAPI.c), but I don't know how this would cause a segfault. Stefan -- Stefan Röhri

Re: [PHP-DEV] segfault in recent code

That fixed part of it, there is still another segfault in there somewhere. Something in the vastness of IMP is making things go weird... On Thu, 1 Aug 2002, Marcus [iso-8859-1] Börger wrote: > At 10:37 01.08.2002, Rasmus Lerdorf wrote: > >/home/rasmus/php4/main/SAPI.c(642) : Block 0x0825B220 sta

Re: [PHP-DEV] segfault in recent code

At 10:37 01.08.2002, Rasmus Lerdorf wrote: >/home/rasmus/php4/main/SAPI.c(642) : Block 0x0825B220 status: >Beginning: Overrun (magic=0x0825B1A8, expected=0x7312F8DC) >[Thu Aug 1 01:32:21 2002] [notice] child pid 24107 exit signal >Segmentation fault (11) > >Poked around for it a bit, but ne

Re: [PHP-DEV] Segfault in current HEAD

At 21:33 12/05/2002, Sebastian Bergmann wrote: >Zeev Suraski wrote: > > This trace isn't meaningful... > > I know. How would I produce a more useful one? It's probably not possible - the best thing to do is to try to cut down the script to the smallest one that still demonstrates the crash. Z

Re: [PHP-DEV] Segfault in current HEAD

Zeev Suraski wrote: > This trace isn't meaningful... I know. How would I produce a more useful one? -- Sebastian Bergmann http://sebastian-bergmann.de/ http://phpOpenTracker.de/ Did I help you? Consider a gift: http://wishlist.sebastian-bergmann.de/ -- PHP Development

Re: [PHP-DEV] Segfault in current HEAD

This trace isn't meaningful... At 20:36 12/05/2002, Sebastian Bergmann wrote: > Can't tell how to reproduce this, it occurs when working with Harald's > form validation system, which is built on top of PEAR::XML_Transformer: > >NTDLL! 778cb892() >NTDLL! 778cb733() >shutdown_memory_manager(int

Re: [PHP-DEV] Segfault with Apache 2.0.35 and PHP 4.2.0

On Mon, 22 Apr 2002, Rasmus Lerdorf wrote: > Try the CVS version of PHP. > > > > I've been having consistent problems trying to get PHP working with > > Apache 2. Basically, after getting everything installed, I try to run > > apache, and everything seems to work until I realise that no apache >

Re: [PHP-DEV] Segfault with Apache 2.0.35 and PHP 4.2.0

Try the CVS version of PHP. On 23 Apr 2002, Leigh Dyer wrote: > Hey guys, > > I've been having consistent problems trying to get PHP working with > Apache 2. Basically, after getting everything installed, I try to run > apache, and everything seems to work until I realise that no apache > tasks

Re: [PHP-DEV] Segfault with current cvs

On Mon, Apr 09, 2001 at 09:33:19PM +0200, Adam Dickmeiss wrote: > this patch seems to fix this. > > RCS file: /repository/php4/ext/standard/dir.c,v > retrieving revision 1.59 > diff -u -r1.59 dir.c > --- dir.c 2001/04/08 21:57:13 1.59 > +++ dir.c 2001/04/09 19:28:43 > @@ -141,7 +141,

RE: [PHP-DEV] Segfault with current cvs

Thanks. Applied, tested and committed. Sean > -Original Message- > From: Adam Dickmeiss [mailto:[EMAIL PROTECTED]] > Sent: Monday, April 09, 2001 3:33 PM > To: Jani Taskinen; [EMAIL PROTECTED] > Subject: Re: [PHP-DEV] Segfault with current cvs > > > Hi, >

Re: [PHP-DEV] Segfault with current cvs

Hi, this patch seems to fix this. RCS file: /repository/php4/ext/standard/dir.c,v retrieving revision 1.59 diff -u -r1.59 dir.c --- dir.c 2001/04/08 21:57:13 1.59 +++ dir.c 2001/04/09 19:28:43 @@ -141,7 +141,7 @@ #endif tmpstr[0] = DEFAULT_SLASH; tmpstr[1] = '\0'; -

Re: [PHP-DEV] Segfault with current cvs

On Mon, Apr 09, 2001 at 09:11:42PM +0200, Jani Taskinen wrote: > >Today's build is giving me this when I try to start Apache with PHP > >compiled as a DSO: > > > >Program received signal SIGSEGV, Segmentation fault. > >0x281cc7b1 in _efree (ptr=0x282c8650) at zend_alloc.c:227 > >227

Re: [PHP-DEV] Segfault with current cvs

Umm..backtrace? --Jani On Mon, 9 Apr 2001, Jon Parise wrote: >Today's build is giving me this when I try to start Apache with PHP >compiled as a DSO: > >Program received signal SIGSEGV, Segmentation fault. >0x281cc7b1 in _efree (ptr=0x282c8650) at zend_alloc.c:227 >227 REM