|  support |  documentation |  report a bug |  advanced search |  search howto |  statistics |  random bug |  login
Bug #17802 php dumps core with ingres extension, not without
Submitted: 2002-06-17 11:18 UTC Modified: 2002-09-11 11:20 UTC
Avg. Score:5.0 ± 0.0
Reproduced:1 of 1 (100.0%)
Same Version:0 (0.0%)
Same OS:0 (0.0%)
From: H dot F dot Schouten at hhs dot nl Assigned:
Status: No Feedback Package: Reproducible crash
PHP Version: 4.2.1 OS: Solaris 2.7
Private report: No CVE-ID: None
View Add Comment Developer Edit
Anyone can comment on a bug. Have a simpler test case? Does it work for you on a different platform? Let us know!
Just going to say 'Me too!'? Don't clutter the database with that please — but make sure to vote on the bug!
Your email address:
Solve the problem:
5 + 41 = ?
Subscribe to this entry?

 [2002-06-17 11:18 UTC] H dot F dot Schouten at hhs dot nl
I have build php-4.2.1 with configure as follows:
./configure --prefix=/test/php-4.2.1 --with-config-file-path=/test/php-4.2.1 --with-mysql=/test/mysql --with-ingres=shared,/usr/local/OI/ingres --enable-trans-sid

When I add in php.ini the line,
the command php dumps core after giving EOF as thus:

prompt> php
X-Powered-By: PHP/4.2.1
Content-type: text/html

Segmentation Fault (core dumped)

Running a php-script with ingres commands works fine, but also ends with a core dump.

Without the ingres extension line no core is dumped...

gdb gives the following backtrace:
(gdb) where
#0  0xfef8ff74 in ?? ()
#1  0xff1d6840 in keys_destruct () from /usr/lib/
#2  0xff1a03e0 in _exithandle () from /usr/lib/
#3  0xff21a194 in exit () from /usr/lib/


Add a Patch

Pull Requests

Add a Pull Request


AllCommentsChangesGit/SVN commitsRelated reports
 [2002-06-17 15:56 UTC]
Does it crash if you compile the Ingres extension as static?

And to generate a useful backtrace, you have to compile PHP
with --enable-debug too. Otherwise the trace is useless.
(to get backtrace, use 'bt' btw..)


 [2002-09-11 11:20 UTC]
No feedback was provided. The bug is being suspended because
we assume that you are no longer experiencing the problem.
If this is not the case and you are able to provide the
information that was requested earlier, please do so and
change the status of the bug back to "Open". Thank you.

PHP Copyright © 2001-2023 The PHP Group
All rights reserved.
Last updated: Wed Feb 08 02:05:49 2023 UTC