I attached basically the same patch over 12 months ago. What can be
done to actually get this patch applied and released?
--
PHP (cli) exits with a segfault if pg_connect() called.
https://bugs.launchpad.net/bugs/63141
You received this bug notification because you are a member of Ubuntu
Server
*** This bug is a duplicate of bug 63141 ***
https://bugs.launchpad.net/bugs/63141
** This bug has been marked a duplicate of bug 63141
PHP (cli) exits with a segfault if pg_connect() called.
--
php5 crashed
https://bugs.launchpad.net/bugs/324313
You received this bug notification
*** This bug is a duplicate of bug 63141 ***
https://bugs.launchpad.net/bugs/63141
** This bug has been marked a duplicate of bug 63141
PHP (cli) exits with a segfault if pg_connect() called.
--
php5 crashed with SIGSEGV in curl_global_cleanup()
https://bugs.launchpad.net/bugs/360947
You
This looks like a duplicate of #63141.
If you are running postgresql as the moodle backend, and have SSL turned
on in the postgresql config (default). I'd be 99.99% sure it's the same
bug.
If this is your configuration, please mark this as a duplicate of the
bug listed in my comment
--
php5
** Changed in: php5 (Ubuntu)
Status: New = Incomplete
--
PHP (Cli) generates invalid output when it exceeds 4kB
https://bugs.launchpad.net/bugs/257892
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to php5 in ubuntu.
--
** CVE added: http://www.cve.mitre.org/cgi-
bin/cvename.cgi?name=2008-3658
** CVE added: http://www.cve.mitre.org/cgi-
bin/cvename.cgi?name=2008-3659
** CVE added: http://www.cve.mitre.org/cgi-
bin/cvename.cgi?name=2008-3660
--
CVE-2008-3658,2008-3659,2008-3660
** Bug watch added: Debian Bug tracker #499987
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=499987
** Also affects: debian via
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=499987
Importance: Unknown
Status: Unknown
--
CVE-2008-3658,2008-3659,2008-3660
Given there are upstream bugs, and a number of people discussing the
bug. Is it safe to say this bug is confirmed rather than new?
--
php5-cgi not working with suphp in Hardy
https://bugs.launchpad.net/bugs/253268
You received this bug notification because you are a member of Ubuntu
Server
This is still a problem in hardy with all updates. I've not checked any
other versions.
I have updated the php bug with comments to see if it will be looked at
further. However due to the nature of the php bug trackers, I'm unable
to change the bug status from No Feedback to Open. Hopefully
Hi,
I've taken the latest version of the PG patch and backported it to 8.3.3
as released in hardy.
Before the application of the below patch, the segfault appears on the
following code;
?php
$conn = pg_connect('host=localhost dbname=postgres sslmode=require');
?
After the patch application.
I can confirm this bug in hardy 8.04
postgresql gives correct output;
[EMAIL PROTECTED]:~$ psql -c select E'\xE2\x80\x99'::varchar
varchar
-
’
php does produces ? as in the report.
** Changed in: php5 (Ubuntu)
Status: New = Confirmed
--
utf8_decode bug
*** This bug is a duplicate of bug 147207 ***
https://bugs.launchpad.net/bugs/147207
** This bug has been marked a duplicate of bug 147207
gutsy php5 crashed with SIGSEGV in CRYPTO_lock()
--
php5 crashed with SIGSEGV in curl_global_cleanup()
https://bugs.launchpad.net/bugs/216869
You
*** This bug is a duplicate of bug 63141 ***
https://bugs.launchpad.net/bugs/63141
** This bug is no longer a duplicate of bug 147207
gutsy php5 crashed with SIGSEGV in CRYPTO_lock()
** This bug has been marked a duplicate of bug 63141
PHP (cli) exits with a segfault if pg_connect()
*** This bug is a duplicate of bug 63141 ***
https://bugs.launchpad.net/bugs/63141
** This bug is no longer a duplicate of bug 147207
gutsy php5 crashed with SIGSEGV in CRYPTO_lock()
** This bug has been marked a duplicate of bug 63141
PHP (cli) exits with a segfault if pg_connect()
*** This bug is a duplicate of bug 63141 ***
https://bugs.launchpad.net/bugs/63141
** This bug is no longer a duplicate of bug 147207
gutsy php5 crashed with SIGSEGV in CRYPTO_lock()
** This bug has been marked a duplicate of bug 63141
PHP (cli) exits with a segfault if pg_connect()
I have marked all the moodle reports as duplicates of this bug. They
exhibit the same symptoms as each other.
The workaround for the pg_connect generic bug is to disable the ssl
connection. Manually altering the moodle connect string in connection
library to disable ssl also removes the
*** This bug is a duplicate of bug 63141 ***
https://bugs.launchpad.net/bugs/63141
** This bug has been marked a duplicate of bug 63141
PHP (cli) exits with a segfault if pg_connect() called.
--
gutsy php5 crashed with SIGSEGV in CRYPTO_lock()
https://bugs.launchpad.net/bugs/147207
You
** Also affects: postgresql-8.3 (Ubuntu)
Importance: Undecided
Status: New
** Changed in: postgresql-8.3 (Ubuntu)
Status: New = Confirmed
--
PHP (cli) exits with a segfault if pg_connect() called.
https://bugs.launchpad.net/bugs/63141
You received this bug notification because
Hi,
After a bit of debugging, some pushing and a big wait, there is a
proposed patch for this. Really this is a bug in PostgreSQL as listed
in the PHP bug report.
I'm not sure if this should be moved. So I'm leaving it here. But it
is certainly a bug in PostgreSQL.
Bug thread reported by me:
Hi,
This doesn't happen to open a postgreSQL connection over SSL does it?
What other libraries does php have loaded for this crash, and what order
are they in?
This appears to be a failure of another library using SSL to do it's
cleanup properly. If you can provide the information above we may
** Changed in: php
Status: New = Confirmed
--
converting some doubles to strings yields trailing colon
https://bugs.launchpad.net/bugs/218891
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to php5 in ubuntu.
--
Ubuntu-server-bugs
I have tested this bug against PHP's snapshot php5.2-200805020830. I
can reproduce it on i386 using the version listed in this comment. I
have logged a bug with PHP.
http://bugs.php.net/bug.php?id=44890
I have not attached the bug URL to the upstream bug as I do now know how
to do it for php
I've run the test in the original test script with slight different
connect parameters on hardy up to date today. I didn't get a crash;
## My php5 conf.d looks like this to load curl.ini and pgsql.ini
[EMAIL PROTECTED]:~$ ls -l /etc/php5/cli/conf.d/
total 16
-rw-r--r-- 1 root root 54 2008-02-28
My understanding is 64bit machines use 64bit integers, so 1 31 doesn't
overflow on 64bit. However on 32bit is does overflow. Even though an
unsigned integer is being printed, a signed integer is being calculated
as shown below;
printf(%s\n, (1 31)); returns -2147483648
This suggests it's
** Changed in: php5 (Ubuntu)
Status: Incomplete = Confirmed
--
number handling in php broken on 32bit system
https://bugs.launchpad.net/bugs/184747
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to php5 in ubuntu.
--
25 matches
Mail list logo
