Req #38917 [Com]: OpenSSL: signing function for spkac

[jason dot gerfen at gmail dot com]

Edit report at https://bugs.php.net/bug.php?id=38917&edit=1

 ID: 38917
 Comment by: jason dot gerfen at gmail dot com
 Reported by:zeph at purotesto dot it
 Summary:OpenSSL: signing function for spkac
 Status: Open
 Type:   Feature/Change Request
 Package:OpenSSL related
 Operating System:   Irrilevant
 PHP Version:4.4.4
 Block user comment: N
 Private report: N

 New Comment:

Not sure how to go about submitting a patch I am working on to address this.


Previous Comments:

[2006-09-21 23:45:19] zeph at purotesto dot it

Description:

i need openssl api support for spkac

now there's the possibility to sign a pkcs10 csr (created by explorer) but not 
an spkac created by firefox/mozilla/netscape/safary ...

check www.openca.org for more information... i need that api to create 
something similar but more usable on the GOsa project http://gosa.gonicus.de

by
Guido Serra

http://dev.purotesto.it/support/gosa
GOsa CA Management plugin







-- 
Edit this bug report at https://bugs.php.net/bug.php?id=38917&edit=1

Req #60432 [Com]: Improving typehinting in function args

[duke at ejoom dot com]

Edit report at https://bugs.php.net/bug.php?id=60432&edit=1

 ID: 60432
 Comment by: duke at ejoom dot com
 Reported by:duke at ejoom dot com
 Summary:Improving typehinting in function args
 Status: Open
 Type:   Feature/Change Request
 Package:Scripting Engine problem
 Operating System:   *
 PHP Version:5.4.0RC2
 Block user comment: N
 Private report: N

 New Comment:

It can be possible to use the function to delete rows in DB:
function delete( array $ids ) { //some code}

delete(3); //will work correct as expected.
// Or
delete(array(3,6));// will work.


Or we would be able to use that behaviour: 
$object->property1 = 1;
$object->property2 = 'value';
tipehind($object);
//where $object converting into array.


Previous Comments:

[2011-12-02 21:12:43] duke at ejoom dot com

Description:

I want to discuss an improving typehint.

I propose to do typehint behaviour as following:
On the Object instance it will behave as current (emit an error).
At the array int and float it must do equivalence:

function typehint( array $array, string $string, int $int, float $float )
{}
   will be equivalent to
function typehint( $array, $string, $int, $float )
{
if (is_array($array) === false) $array = (array) $array;
$string = (string) $string;
$int = (int) $int;
$float = (float) $float;
}

It will do code more readable and compact. For Zend Framework DB it will do 
easier typing query where escaping is based on type of var,

Isn't logical emit error on mismatching of type on int and string at PHP caused 
by easing change type against C or C++. So we must use it feature of PHP and do 
life easier ;).







-- 
Edit this bug report at https://bugs.php.net/bug.php?id=60432&edit=1

[PHP-BUG] Req #60432 [NEW]: Improving typehinting in function args

[duke at ejoom dot com]

From: 
Operating system: *
PHP version:  5.4.0RC2
Package:  Scripting Engine problem
Bug Type: Feature/Change Request
Bug description:Improving typehinting in function args

Description:

I want to discuss an improving typehint.

I propose to do typehint behaviour as following:
On the Object instance it will behave as current (emit an error).
At the array int and float it must do equivalence:

function typehint( array $array, string $string, int $int, float $float )
{}
   will be equivalent to
function typehint( $array, $string, $int, $float )
{
if (is_array($array) === false) $array = (array) $array;
$string = (string) $string;
$int = (int) $int;
$float = (float) $float;
}

It will do code more readable and compact. For Zend Framework DB it will do
easier typing query where escaping is based on type of var,

Isn't logical emit error on mismatching of type on int and string at PHP
caused by easing change type against C or C++. So we must use it feature of
PHP and do life easier ;).


-- 
Edit bug report at https://bugs.php.net/bug.php?id=60432&edit=1
-- 
Try a snapshot (PHP 5.4):
https://bugs.php.net/fix.php?id=60432&r=trysnapshot54
Try a snapshot (PHP 5.3):
https://bugs.php.net/fix.php?id=60432&r=trysnapshot53
Try a snapshot (trunk):  
https://bugs.php.net/fix.php?id=60432&r=trysnapshottrunk
Fixed in SVN:
https://bugs.php.net/fix.php?id=60432&r=fixed
Fixed in SVN and need be documented: 
https://bugs.php.net/fix.php?id=60432&r=needdocs
Fixed in release:
https://bugs.php.net/fix.php?id=60432&r=alreadyfixed
Need backtrace:  
https://bugs.php.net/fix.php?id=60432&r=needtrace
Need Reproduce Script:   
https://bugs.php.net/fix.php?id=60432&r=needscript
Try newer version:   
https://bugs.php.net/fix.php?id=60432&r=oldversion
Not developer issue: 
https://bugs.php.net/fix.php?id=60432&r=support
Expected behavior:   
https://bugs.php.net/fix.php?id=60432&r=notwrong
Not enough info: 
https://bugs.php.net/fix.php?id=60432&r=notenoughinfo
Submitted twice: 
https://bugs.php.net/fix.php?id=60432&r=submittedtwice
register_globals:
https://bugs.php.net/fix.php?id=60432&r=globals
PHP 4 support discontinued:  
https://bugs.php.net/fix.php?id=60432&r=php4
Daylight Savings:https://bugs.php.net/fix.php?id=60432&r=dst
IIS Stability:   
https://bugs.php.net/fix.php?id=60432&r=isapi
Install GNU Sed: 
https://bugs.php.net/fix.php?id=60432&r=gnused
Floating point limitations:  
https://bugs.php.net/fix.php?id=60432&r=float
No Zend Extensions:  
https://bugs.php.net/fix.php?id=60432&r=nozend
MySQL Configuration Error:   
https://bugs.php.net/fix.php?id=60432&r=mysqlcfg

Bug #60423 [Opn->Bgs]: Segmentation fault with the UTF-8 check regexp in some cases

[felipe]

Edit report at https://bugs.php.net/bug.php?id=60423&edit=1

 ID: 60423
 Updated by: fel...@php.net
 Reported by:amal dot samally at gmail dot com
 Summary:Segmentation fault with the UTF-8 check regexp in
 some cases
-Status: Open
+Status: Bogus
 Type:   Bug
 Package:PCRE related
 Operating System:   Linux
 PHP Version:5.3.8
 Block user comment: N
 Private report: N

 New Comment:

Sorry, but your problem does not imply a bug in PHP itself.  For a
list of more appropriate places to ask for help using PHP, please
visit http://www.php.net/support.php as this bug system is not the
appropriate forum for asking support questions.  Due to the volume
of reports we can not explain in detail here why your report is not
a bug.  The support channels will be able to provide an explanation
for you.

Thank you for your interest in PHP.

It's a known behavior from PCRE. Check out other bugs reports or the PCRE 
documentation.


Previous Comments:

[2011-12-02 12:29:48] amal dot samally at gmail dot com

gdb output:

(gdb) run test.php
Starting program: /usr/local/bin/php test.php
[Thread debugging using libthread_db enabled]

Program received signal SIGSEGV, Segmentation fault.
0x00498948 in match (
eptr=0x139a566 "1{font-weight:bold}#gbg6.gbgt-
hvr,#gbg6.gbgt:focus{background-color:transparent;background-
image:none}.gbg4a{font-size:0;line-height:0}.gbg4a .gbts{padding:27px 5px 
0;*padding:25px 5px 0}.gbto .gbg4a "..., ecode=0x13d9525 "^", 
mstart=0x13990f0 "   docs.pravo.ru - 
Поиск в 
Google   

Bug #60431 [Bgs]: private Array

[pajoye]

Edit report at https://bugs.php.net/bug.php?id=60431&edit=1

 ID: 60431
 Updated by: paj...@php.net
 Reported by:kapsonfire at gmx dot de
 Summary:private Array
 Status: Bogus
 Type:   Bug
 Package:Class/Object related
 Operating System:   Debian Squeeze
 PHP Version:5.3.8
 Block user comment: N
 Private report: N

 New Comment:

No, it is not readable. Using:

class Item {
   private $DATA=array();
   private $OWNER=null;
   public function __construct($itemID) {
   }
}
$a = new Item(1);
$a->DATA;

PHP Fatal error:  Cannot access private property Item::$DATA in 
/home/pierre/60431.php on line 14


Previous Comments:

[2011-12-02 12:15:11] kapsonfire at gmx dot de

Well, but this only happens with arrays used as datalayer in this way.
The $OWNER isn't readable outside with print_r after creating an instance on it.


[2011-12-02 12:11:33] paj...@php.net

Release\php.exe -n -r "class f {private $f=1;} $a = new f; $a->f;"

Fatal error: Cannot access private property f::$f in Command line code on line 1

print_r/var_dump are only a debugging/informative functions.


[2011-12-02 12:03:45] kapsonfire at gmx dot de

Description:

Using an private array in a Class as Data Layer become readale outside of class 
with print_r

Test script:
---
ITEMOBJECT:".(print_r($item,true))."";
?>



DATA[$key] = $item[$key];
}

}

   
}


Expected result:

ITEMOBJECT:
Item Object
(
[DATA:Item:private] => Array
(
[itemid] => 1
[uid] => 2
)

[OWNER:Item:private] => 
)







-- 
Edit this bug report at https://bugs.php.net/bug.php?id=60431&edit=1

Bug #60423 [Fbk->Opn]: Segmentation fault with the UTF-8 check regexp in some cases

[amal dot samally at gmail dot com]

Edit report at https://bugs.php.net/bug.php?id=60423&edit=1

 ID: 60423
 User updated by:amal dot samally at gmail dot com
 Reported by:amal dot samally at gmail dot com
 Summary:Segmentation fault with the UTF-8 check regexp in
 some cases
-Status: Feedback
+Status: Open
 Type:   Bug
 Package:PCRE related
 Operating System:   Linux
 PHP Version:5.3.8
 Block user comment: N
 Private report: N

 New Comment:

gdb output:

(gdb) run test.php
Starting program: /usr/local/bin/php test.php
[Thread debugging using libthread_db enabled]

Program received signal SIGSEGV, Segmentation fault.
0x00498948 in match (
eptr=0x139a566 "1{font-weight:bold}#gbg6.gbgt-
hvr,#gbg6.gbgt:focus{background-color:transparent;background-
image:none}.gbg4a{font-size:0;line-height:0}.gbg4a .gbts{padding:27px 5px 
0;*padding:25px 5px 0}.gbto .gbg4a "..., ecode=0x13d9525 "^", 
mstart=0x13990f0 "   docs.pravo.ru - 
Поиск в 
Google   

Bug #49660 [Opn->Csd]: libxml 2.7.3+ limits text nodes to 10MB

[gooh]

Edit report at https://bugs.php.net/bug.php?id=49660&edit=1

 ID: 49660
 Updated by: g...@php.net
 Reported by:sta at netimage dot dk
 Summary:libxml 2.7.3+ limits text nodes to 10MB
-Status: Open
+Status: Closed
 Type:   Bug
 Package:SOAP related
 Operating System:   FreeBSD 7.1
 PHP Version:*
-Assigned To:
+Assigned To:gooh
 Block user comment: N
 Private report: N



Previous Comments:

[2009-12-01 11:15:18] fel...@php.net

"Added LIBXML_PARSEHUGE constant to overrides the maximum text size of a single 
text node when using libxml2.7.3+."


[2009-12-01 02:06:10] fel...@php.net

This bug has been fixed in SVN.

Snapshots of the sources are packaged every three hours; this change
will be in the next snapshot. You can grab the snapshot at
http://snaps.php.net/.
 
Thank you for the report, and for helping us make PHP better.




[2009-12-01 02:05:29] s...@php.net

Automatic comment from SVN on behalf of felipe
Revision: http://svn.php.net/viewvc/?view=revision&revision=291533
Log: - Fixed bug #49660 (libxml 2.7.3+ limits text nodes to 10MB). (Felipe)
- Added LIBXML_PARSEHUGE constant to overrides the maximum text size of a
  single text node when using libxml2.7.3+. (Kalle)
[DOC]


[2009-09-28 11:31:14] sta at netimage dot dk

Hi Kalle.

Thanks for replying so soon.

Your patch does fix the issue when loading directly with 
simplexml_load_file('file.xml', 'SimpleXMLElement', LIBXML_PARSEHUGE);

However the error was not originally encountered using simplexml, but using 
SoapClient - and there does not seem to be a way to pass libxml-options to 
SoapClient.

So as far as I can tell, the problem remains when using SoapClient.

/Thing


[2009-09-26 12:12:14] ka...@php.net

I guess we could expose the constant value from ext/libxml if available like:
Index: libxml.c
===
--- libxml.c(revision 288659)
+++ libxml.c(working copy)
@@ -622,6 +622,9 @@
REGISTER_LONG_CONSTANT("LIBXML_COMPACT",XML_PARSE_COMPACT,  
CONST_CS | CONST_PERSISTENT);
REGISTER_LONG_CONSTANT("LIBXML_NOXMLDECL",  XML_SAVE_NO_DECL,   
CONST_CS | CONST_PERSISTENT);
 #endif
+#if LIBXML_VERSION >= 20703
+   REGISTER_LONG_CONSTANT("LIBXML_PARSEHUGE",  XML_PARSE_HUGE, 
CONST_CS | CONST_PERSISTENT);
+#endif
REGISTER_LONG_CONSTANT("LIBXML_NOEMPTYTAG", LIBXML_SAVE_NOEMPTYTAG, 
CONST_CS | CONST_PERSISTENT);
 
/* Error levels */


Does this work for you when passing it to SimpleXML's $option parameter?

(Patch made against PHP_5_3, but is just a 3 line c/p to other branches)




The remainder of the comments for this report are too long. To view
the rest of the comments, please view the bug report online at

https://bugs.php.net/bug.php?id=49660


-- 
Edit this bug report at https://bugs.php.net/bug.php?id=49660&edit=1

Bug #60431 [Com]: private Array

[kapsonfire at gmx dot de]

Edit report at https://bugs.php.net/bug.php?id=60431&edit=1

 ID: 60431
 Comment by: kapsonfire at gmx dot de
 Reported by:kapsonfire at gmx dot de
 Summary:private Array
 Status: Bogus
 Type:   Bug
 Package:Class/Object related
 Operating System:   Debian Squeeze
 PHP Version:5.3.8
 Block user comment: N
 Private report: N

 New Comment:

Well, but this only happens with arrays used as datalayer in this way.
The $OWNER isn't readable outside with print_r after creating an instance on it.


Previous Comments:

[2011-12-02 12:11:33] paj...@php.net

Release\php.exe -n -r "class f {private $f=1;} $a = new f; $a->f;"

Fatal error: Cannot access private property f::$f in Command line code on line 1

print_r/var_dump are only a debugging/informative functions.


[2011-12-02 12:03:45] kapsonfire at gmx dot de

Description:

Using an private array in a Class as Data Layer become readale outside of class 
with print_r

Test script:
---
ITEMOBJECT:".(print_r($item,true))."";
?>



DATA[$key] = $item[$key];
}

}

   
}


Expected result:

ITEMOBJECT:
Item Object
(
[DATA:Item:private] => Array
(
[itemid] => 1
[uid] => 2
)

[OWNER:Item:private] => 
)







-- 
Edit this bug report at https://bugs.php.net/bug.php?id=60431&edit=1

Bug #53626 [Com]: SQLite3 - Segmentation Fault on shutdown

[sb at litepc dot com]

Edit report at https://bugs.php.net/bug.php?id=53626&edit=1

 ID: 53626
 Comment by: sb at litepc dot com
 Reported by:bion at drewcrawfordapps dot com
 Summary:SQLite3 - Segmentation Fault on shutdown
 Status: Verified
 Type:   Bug
 Package:Reproducible crash
 Operating System:   Mac OS X 10.7.1
 PHP Version:5.3.8
 Block user comment: N
 Private report: N

 New Comment:

Additional Info:  reducing extensions.ini to only sqlite3.so (no other modules 
loaded) also gave the Segmentation fault when executing /usr/local/bin/php-cgi 
-v


Previous Comments:

[2011-12-02 08:33:23] sb at litepc dot com

I get a segfault whenever php-cgi exits even without using sqlite functions.

FreeBSD.  Latest Ports as of 1/12/2011

php5-5.3.8
php5-pdo_sqlite-5.3.8
php5-sqlite-5.3.8
php5-sqlite3-5.3.8
sqlite3-3.7.9


# /usr/local/bin/php-cgi -v
PHP 5.3.8 with Suhosin-Patch (cgi-fcgi) (built: Dec  1 2011 22:33:51)
Copyright (c) 1997-2011 The PHP Group
Zend Engine v2.3.0, Copyright (c) 1998-2011 Zend Technologies
Segmentation fault
#

Editing extensions.ini to comment out sqlite3.so *and* pdo_sqlite.so  
eliminates the Segmentation fault error.

With respect to: "This is due the destructor order."

I have tried many permutations of ordering in extensions.ini but found no case 
where enabling sqlite3.so or pdo_sqlite.so worked in any position.

Can not recompile with debug yet as this is a production machine... but will 
attempt to reproduce in test scenario and update.


[2011-09-23 04:55:13] bion at drewcrawfordapps dot com

This bug is still reproducible, and in fact has regressed, since I no longer 
get a 
helpful console error message, but a generic crash report. What are the chances 
of 
getting this fixed?


[2011-06-05 20:28:48] fel...@php.net

This is due the destructor order.


[2011-03-08 20:15:05] bionoren at letu dot edu

It's more helpful. I get the following messages in the Apache error log:
test/index.php(14) : Warning - SQLite3::query() [sqlite3.query]: table test already exists
test/index.php(3) : Catchable fatal error - Argument 1 passed to 
test::__construct() must be an array, boolean given, called in test/index.php 
on line 9 and defined
[Tue Mar 08 13:11:41 2011] [notice] child pid 26396 exit signal Segmentation 
fault (11)

Here's the stack trace:
Program received signal EXC_BAD_ACCESS, Could not access memory.
Reason: 13 at address: 0x
0x0001015d0831 in zend_llist_del_element (l=0x10071c0f0, 
element=0x10208c258, compare=0x10109f549 ) at 
/Users/bion/Downloads/php5.3-201103081730/Zend/zend_llist.c:97
97  next = current->next;


[2011-03-08 18:00:04] fel...@php.net

Please try using this snapshot:

  http://snaps.php.net/php5.3-latest.tar.gz
 
For Windows:

  http://windows.php.net/snapshots/






The remainder of the comments for this report are too long. To view
the rest of the comments, please view the bug report online at

https://bugs.php.net/bug.php?id=53626


-- 
Edit this bug report at https://bugs.php.net/bug.php?id=53626&edit=1

Bug #60431 [Opn->Bgs]: private Array

[pajoye]

Edit report at https://bugs.php.net/bug.php?id=60431&edit=1

 ID: 60431
 Updated by: paj...@php.net
 Reported by:kapsonfire at gmx dot de
 Summary:private Array
-Status: Open
+Status: Bogus
 Type:   Bug
 Package:Class/Object related
 Operating System:   Debian Squeeze
 PHP Version:5.3.8
 Block user comment: N
 Private report: N

 New Comment:

Release\php.exe -n -r "class f {private $f=1;} $a = new f; $a->f;"

Fatal error: Cannot access private property f::$f in Command line code on line 1

print_r/var_dump are only a debugging/informative functions.


Previous Comments:

[2011-12-02 12:03:45] kapsonfire at gmx dot de

Description:

Using an private array in a Class as Data Layer become readale outside of class 
with print_r

Test script:
---
ITEMOBJECT:".(print_r($item,true))."";
?>



DATA[$key] = $item[$key];
}

}

   
}


Expected result:

ITEMOBJECT:
Item Object
(
[DATA:Item:private] => Array
(
[itemid] => 1
[uid] => 2
)

[OWNER:Item:private] => 
)







-- 
Edit this bug report at https://bugs.php.net/bug.php?id=60431&edit=1

[PHP-BUG] Bug #60431 [NEW]: private Array

[kapsonfire at gmx dot de]

From: 
Operating system: Debian Squeeze
PHP version:  5.3.8
Package:  Class/Object related
Bug Type: Bug
Bug description:private Array

Description:

Using an private array in a Class as Data Layer become readale outside of
class with print_r

Test script:
---
ITEMOBJECT:".(print_r($item,true))."";
?>



DATA[$key] = $item[$key];
}

}

   
}


Expected result:

ITEMOBJECT:
Item Object
(
[DATA:Item:private] => Array
(
[itemid] => 1
[uid] => 2
)

[OWNER:Item:private] => 
)


-- 
Edit bug report at https://bugs.php.net/bug.php?id=60431&edit=1
-- 
Try a snapshot (PHP 5.4):
https://bugs.php.net/fix.php?id=60431&r=trysnapshot54
Try a snapshot (PHP 5.3):
https://bugs.php.net/fix.php?id=60431&r=trysnapshot53
Try a snapshot (trunk):  
https://bugs.php.net/fix.php?id=60431&r=trysnapshottrunk
Fixed in SVN:
https://bugs.php.net/fix.php?id=60431&r=fixed
Fixed in SVN and need be documented: 
https://bugs.php.net/fix.php?id=60431&r=needdocs
Fixed in release:
https://bugs.php.net/fix.php?id=60431&r=alreadyfixed
Need backtrace:  
https://bugs.php.net/fix.php?id=60431&r=needtrace
Need Reproduce Script:   
https://bugs.php.net/fix.php?id=60431&r=needscript
Try newer version:   
https://bugs.php.net/fix.php?id=60431&r=oldversion
Not developer issue: 
https://bugs.php.net/fix.php?id=60431&r=support
Expected behavior:   
https://bugs.php.net/fix.php?id=60431&r=notwrong
Not enough info: 
https://bugs.php.net/fix.php?id=60431&r=notenoughinfo
Submitted twice: 
https://bugs.php.net/fix.php?id=60431&r=submittedtwice
register_globals:
https://bugs.php.net/fix.php?id=60431&r=globals
PHP 4 support discontinued:  
https://bugs.php.net/fix.php?id=60431&r=php4
Daylight Savings:https://bugs.php.net/fix.php?id=60431&r=dst
IIS Stability:   
https://bugs.php.net/fix.php?id=60431&r=isapi
Install GNU Sed: 
https://bugs.php.net/fix.php?id=60431&r=gnused
Floating point limitations:  
https://bugs.php.net/fix.php?id=60431&r=float
No Zend Extensions:  
https://bugs.php.net/fix.php?id=60431&r=nozend
MySQL Configuration Error:   
https://bugs.php.net/fix.php?id=60431&r=mysqlcfg

Bug #53626 [Com]: SQLite3 - Segmentation Fault on shutdown

[sb at litepc dot com]

Edit report at https://bugs.php.net/bug.php?id=53626&edit=1

 ID: 53626
 Comment by: sb at litepc dot com
 Reported by:bion at drewcrawfordapps dot com
 Summary:SQLite3 - Segmentation Fault on shutdown
 Status: Verified
 Type:   Bug
 Package:Reproducible crash
 Operating System:   Mac OS X 10.7.1
 PHP Version:5.3.8
 Block user comment: N
 Private report: N

 New Comment:

I get a segfault whenever php-cgi exits even without using sqlite functions.

FreeBSD.  Latest Ports as of 1/12/2011

php5-5.3.8
php5-pdo_sqlite-5.3.8
php5-sqlite-5.3.8
php5-sqlite3-5.3.8
sqlite3-3.7.9


# /usr/local/bin/php-cgi -v
PHP 5.3.8 with Suhosin-Patch (cgi-fcgi) (built: Dec  1 2011 22:33:51)
Copyright (c) 1997-2011 The PHP Group
Zend Engine v2.3.0, Copyright (c) 1998-2011 Zend Technologies
Segmentation fault
#

Editing extensions.ini to comment out sqlite3.so *and* pdo_sqlite.so  
eliminates the Segmentation fault error.

With respect to: "This is due the destructor order."

I have tried many permutations of ordering in extensions.ini but found no case 
where enabling sqlite3.so or pdo_sqlite.so worked in any position.

Can not recompile with debug yet as this is a production machine... but will 
attempt to reproduce in test scenario and update.


Previous Comments:

[2011-09-23 04:55:13] bion at drewcrawfordapps dot com

This bug is still reproducible, and in fact has regressed, since I no longer 
get a 
helpful console error message, but a generic crash report. What are the chances 
of 
getting this fixed?


[2011-06-05 20:28:48] fel...@php.net

This is due the destructor order.


[2011-03-08 20:15:05] bionoren at letu dot edu

It's more helpful. I get the following messages in the Apache error log:
test/index.php(14) : Warning - SQLite3::query() [sqlite3.query]: table test already exists
test/index.php(3) : Catchable fatal error - Argument 1 passed to 
test::__construct() must be an array, boolean given, called in test/index.php 
on line 9 and defined
[Tue Mar 08 13:11:41 2011] [notice] child pid 26396 exit signal Segmentation 
fault (11)

Here's the stack trace:
Program received signal EXC_BAD_ACCESS, Could not access memory.
Reason: 13 at address: 0x
0x0001015d0831 in zend_llist_del_element (l=0x10071c0f0, 
element=0x10208c258, compare=0x10109f549 ) at 
/Users/bion/Downloads/php5.3-201103081730/Zend/zend_llist.c:97
97  next = current->next;


[2011-03-08 18:00:04] fel...@php.net

Please try using this snapshot:

  http://snaps.php.net/php5.3-latest.tar.gz
 
For Windows:

  http://windows.php.net/snapshots/




[2010-12-29 01:07:56] bionoren at letu dot edu

query("SELECT * from test");
return new test($result->fetchArray(SQLITE3_ASSOC));
}
}

$db = new SQLite3("test.sqlite", SQLITE3_OPEN_READWRITE | 
SQLITE3_OPEN_CREATE);
$db->query("CREATE TABLE test (foo, bar)");

test::getInstance($db);
print "done";
?>




The remainder of the comments for this report are too long. To view
the rest of the comments, please view the bug report online at

https://bugs.php.net/bug.php?id=53626


-- 
Edit this bug report at https://bugs.php.net/bug.php?id=53626&edit=1