Bug #16291 Updated: pg_last_notice causes SegFault
| From: | sander@php.net | Date: | Tue, 26 Mar 2002 17:55:22 +0000 |
| Subject: | Bug #16291 Updated: pg_last_notice causes SegFault | ||
| References: | 1 | Groups: | php.bugs |
| Request: | Send a blank email to php-bugs+get-3409@lists.php.net to get a copy of this message | ||
ID: 16291
Updated by: sander@php.net
Reported By: cecot@dirbg.com
-Status: Open
+Status: Feedback
Bug Type: Reproducible crash
Operating System: linux MDK 8.1
PHP Version: 4.1.2
New Comment:
We can't do much without a backtrace. Can you try to get one? See
http://bugs.php.net/bugs-generating-backtrace.php
for instructions.
Previous Comments:
------------------------------------------------------------------------
[2002-03-26 12:37:33] cecot@dirbg.com
pg_last_notice() causes segmentation falts when the postgresql
generates notices. I mean when there are no messages from the DB server
(RAISE NOTICE ....), pg_last_notice does not generate errors, but when
the DB server generates notices they are sent to the apache log file
(which I find strange), and with them SegFault for the apache child.
I used php-4.1.2 the bug is presented, I get the CVS from 25 March and
the problem still exists.
P.S. if it is necessary I may try to generate backtrace, but the last
time I tried I didn't succeeded :(
------------------------------------------------------------------------
--
Edit this bug report at http://bugs.php.net/?id=16291&edit=1