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
13 matches
Mail list logo
