Use zend_get_gc_buffer_add_fcc()

Fix build with sqlite3 gc and fci/fcc api

Merge branch 'PHP-8.2' into PHP-8.3

* PHP-8.2:
Fix GH-11878: SQLite3 callback functions cause a memory leak with a callable array

Merge branch 'PHP-8.1' into PHP-8.2

* PHP-8.1:
Fix GH-11878: SQLite3 callback functions cause a memory leak with a callable array

Fix GH-11878: SQLite3 callback functions cause a memory leak with a callable array

In this test file, the free_obj handler is called with a refcount of 2,
caused by the fact we do a GC_A

Fix GH-11878: SQLite3 callback functions cause a memory leak with a callable array

In this test file, the free_obj handler is called with a refcount of 2,
caused by the fact we do a GC_ADDREF() to increase its refcount while
its refcount is still 1 because the Foo object hasn't been destroyed yet
(due to the cycle caused by the sqlite function callback).
Solve this by introducing a get_gc handler.

Closes GH-11881.

show more ...

Revert "Skip profiling of sqlite3_step"

This reverts commit bb31a75321c1b6cc060568fe0b3f123d1a72d67d.

It doesn't seem like this actually fixed the problem.

Skip profiling of sqlite3_step

It looks like sqlite3_step can vary quite drastically from one request to the
next. This seems to be caused by more or fewer calls to sqlite3VdbeSorterWrit

Skip profiling of sqlite3_step

It looks like sqlite3_step can vary quite drastically from one request to the
next. This seems to be caused by more or fewer calls to sqlite3VdbeSorterWrite.
It would be great if we could find a way to make execution of this function more
consistent, but at this point I don't know how.

Closes GH-12130

show more ...

Merge branch 'PHP-8.2'

* PHP-8.2:
Fix replaced error handling in SQLite3Stmt::__construct

Merge branch 'PHP-8.1' into PHP-8.2

* PHP-8.1:
Fix replaced error handling in SQLite3Stmt::__construct

Fix replaced error handling in SQLite3Stmt::__construct

The error handling is replaced using zend_replace_error_handling(), but
when SQLITE3_CHECK_INITIALIZED() returns early, the old er

Fix replaced error handling in SQLite3Stmt::__construct

The error handling is replaced using zend_replace_error_handling(), but
when SQLITE3_CHECK_INITIALIZED() returns early, the old error handling
isn't restored.

In the past, SQLITE3_CHECK_INITIALIZED() threw a warning when the check
failed. This was replaced a few years ago with an error exception. So we
can fix the bug by just removing the replacing error handling as it
accomplishes nothing anymore.

Closes GH-11607.

show more ...

[RFC] Transition SQLite3 to exceptions (#11058)

* Deprecate warnings in SQLite3, change returned exception class to SQLite3Exception

RFC: https://wiki.php.net/rfc/sqlite3_exceptions

[RFC] Transition SQLite3 to exceptions (#11058)

* Deprecate warnings in SQLite3, change returned exception class to SQLite3Exception

RFC: https://wiki.php.net/rfc/sqlite3_exceptions

Co-authored-by: Tim Düsterhus <timwolla@googlemail.com>

show more ...

Merge branch 'PHP-8.2'

* PHP-8.2:
Fix GH-11451: Invalid associative array containing duplicate keys

Fix GH-11451: Invalid associative array containing duplicate keys

It used the "add_new" variant which assumes the key doesn't already
exist. But in case of duplicate keys we have to take

Fix GH-11451: Invalid associative array containing duplicate keys

It used the "add_new" variant which assumes the key doesn't already
exist. But in case of duplicate keys we have to take the last result.

Closes GH-11453.

show more ...

ext: make various internal functions static (#10650)

Namely in:
* ext/date
* ext/libxml
* ext/dba
* ext/curl

Make lots of string pointers `const` (#10646)

This allows using string literals without implicitly casting away the
`const`.

Merge branch 'PHP-8.2'

* PHP-8.2:
Fix #81742: open_basedir bypass in SQLite3 by using file URI

Merge branch 'PHP-8.1' into PHP-8.2

* PHP-8.1:
Fix #81742: open_basedir bypass in SQLite3 by using file URI

Fix #81742: open_basedir bypass in SQLite3 by using file URI

A previous fix[1] was not sufficient to catch all potential file URIs,
because the patch did not cater to URL encoding. Prop

Fix #81742: open_basedir bypass in SQLite3 by using file URI

A previous fix[1] was not sufficient to catch all potential file URIs,
because the patch did not cater to URL encoding. Properly parsing and
decoding the URI may yield a different result than the handling of
SQLite3, so we play it safe, and reject any file URIs if open_basedir
is configured.

[1] <https://bugs.php.net/bug.php?id=77967>

Closes GH-10018.

show more ...

Handle trampolines correctly in new FCC API + usages (#9877)

Only use FCC for SQLite3 user defined authorizer

Only use FCC for SQLite3 user defined collations

Only use FCC for SQLite3 user defined functions

Revert "Port all internally used classes to use default_object_handlers"

This reverts commit 94ee4f9834743ca74f6c9653863273277ce6c61a.

The commit was a bit too late to be included i

Revert "Port all internally used classes to use default_object_handlers"

This reverts commit 94ee4f9834743ca74f6c9653863273277ce6c61a.

The commit was a bit too late to be included in PHP 8.2 RC1. Given it's a massive ABI break, we decide to postpone the change to PHP 8.3.

show more ...

Use php_info_print_table_header for actual column headers only (#9485)

Using php_info_print_table_header() for "Foo: bar" looks odd and out of place,
because the whole line is colored. I

Use php_info_print_table_header for actual column headers only (#9485)

Using php_info_print_table_header() for "Foo: bar" looks odd and out of place,
because the whole line is colored. It is also questionable from a HTML
semantics point of view, because it does not described the columns that follow.

The use of this across extensions is inconsistent. It was part of the skeleton,
but ext/date or ext/json already use a regular row.

show more ...

Port all internally used classes to use default_object_handlers

Signed-off-by: Bob Weinand <bobwei9@hotmail.com>