What I meant to say was that I did use zend_fetch_list_dtor_id in RINIT
at
first, but I noticed that PHP was not calling RINIT. So then I migrated it
MINIT, which is called when the module is loaded.
Doubtful... PHP calls every module's RINIT at the start of every request.
If you were "testin
> both claims above don't make *any* sense to me, making me think
> you still really do not know what you are doing :(
O_O, wow, sorry...
I did not write that like that..
What I meant to say was that I did use zend_fetch_list_dtor_id in RINIT at
first, but I noticed that PHP was not calling RI
RG wrote:
Well I did try to use it in RINIT, but PHP just wasn't RINIT so I
figured why not put it in MINIT.
...
> I used malloc
instead of emalloc, so malloc was causing gcc to miscalculate its size or
make it quit with an error.
both claims above don't make *any* sense to me, making m
Sebastian Bergmann wrote:
> Here is the correct stacktrace.
I now worked around the segfault.
--
Sebastian Bergmann http://www.sebastian-bergmann.de/
GnuPG Key: 0xB85B5D69 / 27A7 2B14 09E4 98CD 6277 0E5B 6867 C514 B85B 5D69
--
PHP Internals - PHP Runtime Development Maili
On Mon, 2004-03-01 at 16:53, [EMAIL PROTECTED] wrote:
> >This should be fixed now. Thanks for the short reproducing script.
> >
> >Andi
>
> I don't think, that it is fixed in latest cvs.
> Simply changing the script to this, the problem/bug still exists:
[...]
$ cat destruct_segfault.php
foo = fa
On Tue, 2004-02-24 at 22:45, Jani Taskinen wrote:
> This is most likely fixed already in CVS.
>
> --Jani
It wasn't yesterday, but now it is:) I was able to reproduce it but
couldn't come up with a simple script demonstrating the behaviour.
- Timm
--
PHP Internals - PHP Runtime Deve
This is most likely fixed already in CVS.
--Jani
p.s. ALWAYS try the latest snapshot first before submitting
any bug report / sending any mails.
On Tue, 24 Feb 2004, Hans Lellelid wrote:
>Hi - I know that this segfault report is quite vague. Can anyone tell
>me
Paul Eggert wrote:
> 2003-10-06 Paul Eggert <[EMAIL PROTECTED]>
>
> * Zend/zend_ini_parser.y:
> This fixes PHP bugs #25770 and #21159.
Seems fixed indeed, no longer segfaults on my GENTOO/Linux laptop with
bison 1.875.
Thanks Paul,
Sebastian
--
Sebastian Bergmann
http://se
"Wez Furlong" <[EMAIL PROTECTED]> writes:
> The original response to this issue from the bison people was the
> not very encouraging "thou shalt not use the skeleton file".
> ... the bison team had made it apparent in the past
> that they were not interested in fixing the problem.
Sorry, I don't
Rasmus Lerdorf <[EMAIL PROTECTED]> writes:
> You need a php.ini file to reproduce the problem.
OK, thanks. With everybody's help I reproduced the problem.
It turns out to be a portability bug in Zend/zend_ini_parser.y.
That grammar uses the character constant '\0' as a token.
POSIX says that th
On 6 Oct 2003, Paul Eggert wrote:
> Here's how I tried to reproduce the problem. I am running Debian
> GNU/Linux 3.0r1 (stable) with Bison 1.875.
You need a php.ini file to reproduce the problem. Here is how to figure
out where it wants it:
% php -i | grep ini
Configuration File (php.ini) Path
Zeev Suraski <[EMAIL PROTECTED]> writes:
> Do you experience this bug with PHP 4.3.2?
Here's how I tried to reproduce the problem. I am running Debian
GNU/Linux 3.0r1 (stable) with Bison 1.875.
wget http://downloads.php.net/ilia/php-4.3.4RC1.tar.bz2
tar xjf php-4.3.4RC1.tar.bz2
cd php-4.3
At 18:50 06/10/2003, Rasmus Lerdorf wrote:
The bug is there with the current PHP4_3 HEAD. Haven't tried compiling
4.3.2 with 1.875.
Well, judging by the suggested patch at the report for bug #22215, it
appears it might be somehow related to the fd patch, so it's interesting to
see whether 4.3.2
> > Just don't use bison 1.875
> If you can't help us solve the problem, fine; but please don't
> discourage other people from helping.
Step back a moment and consider...
The original response to this issue from the bison people was the
not very encouraging "thou shalt not use the skeleton fi
The bug is there with the current PHP4_3 HEAD. Haven't tried compiling
4.3.2 with 1.875.
-Rasmus
On Mon, 6 Oct 2003, Zeev Suraski wrote:
> Do you experience this bug with PHP 4.3.2?
>
> Zeev
>
> At 18:29 06/10/2003, Paul Eggert wrote:
> >"Wez Furlong" <[EMAIL PROTECTED]> writes:
> >
> > > Ju
Do you experience this bug with PHP 4.3.2?
Zeev
At 18:29 06/10/2003, Paul Eggert wrote:
"Wez Furlong" <[EMAIL PROTECTED]> writes:
> Just don't use bison 1.875
We're trying to get the Bison bug (if there is one) fixed.
Possibly the bug is in flex, or is in PHP itself.
I understand that the P
"Wez Furlong" <[EMAIL PROTECTED]> writes:
> Just don't use bison 1.875
We're trying to get the Bison bug (if there is one) fixed.
Possibly the bug is in flex, or is in PHP itself.
I understand that the PHP folks prefer to use older version of
software tools if they happen to work, and that's
Just don't use bison 1.875
--Wez.
- Original Message -
From: "Paul Eggert" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Cc: <[EMAIL PROTECTED]>; <[EMAIL PROTECTED]>
Sent: Monday, October 06, 2003 6:24 AM
Subject: [PHP-DEV] Re: Segfault with PHP and bison 1.875(a)
> Martin Schlemmer
On Sun, 5 Oct 2003, Rasmus Lerdorf wrote:
> I had a look at this. I think it is only the ini file parser that is
> crashing. Try running without a php.ini. Not that this is ok, but it at
> least narrows it down a bit if true.
Oh, never mind, just read the bug report all the way to the end and
I had a look at this. I think it is only the ini file parser that is
crashing. Try running without a php.ini. Not that this is ok, but it at
least narrows it down a bit if true.
-Rasmus
On Sun, 5 Oct 2003, Sebastian Bergmann wrote:
> Paul Eggert wrote:
> >> http://bugs.php.net/bug.php?id=2
20 matches
Mail list logo
