Ah off couse,
It's not giving the segmentation fault on the first test. Thats even
stranger. It appears that the system admin had updated the kernel, than
updated some more software and than put back the old kernel. It's still
strange.
Arnold
Sebastian Bergmann wrote:
> Arnold Daniels wrote:
>
Arnold Daniels wrote:
> I've got no idea where the the stands for.
PHPUnit reports progress with .FEIS characters, see
http://www.phpunit.de/pocket_guide/3.0/en/textui.html for details.
--
Sebastian Bergmann http://sebastian-bergmann.de/
GnuPG Key: 0xB85B5D69 / 27
On Mon, 15 Jan 2007, Arnold Daniels wrote:
> Hi again,
>
> First of all thanks for your reply. It sound logical, but doesn't work
> unfortunately. I now get:
>
>seabert:/var/pear# phpunit Test_Standard_qconf
>PHPUnit 3.0.0alpha11 by Sebastian Bergmann.
>
>Segmentation fault
>
>
On 01/16/2007 12:12 AM, Arnold Daniels wrote:
Hi again,
First of all thanks for your reply. It sound logical, but doesn't work
unfortunately. I now get:
seabert:/var/pear# phpunit Test_Standard_qconf
PHPUnit 3.0.0alpha11 by Sebastian Bergmann.
Segmentation fault
I've got no
Hi again,
First of all thanks for your reply. It sound logical, but doesn't work
unfortunately. I now get:
seabert:/var/pear# phpunit Test_Standard_qconf
PHPUnit 3.0.0alpha11 by Sebastian Bergmann.
Segmentation fault
I've got no idea where the the stands for.
/**
* Parse .
On 01/15/2007 11:50 PM, Arnold Daniels wrote:
Hi,
I could use some help on an extension I've written. It worked fine
before, but from out the blue I started to get segmentation faults. I've
located it down to this piece of code, but I don't do any writes to the
code memory, so I don't get wha
Hi,
I could use some help on an extension I've written. It worked fine
before, but from out the blue I started to get segmentation faults. I've
located it down to this piece of code, but I don't do any writes to the
code memory, so I don't get what's wrong. It seems like the error lies
in the
