Bug #20201 | Segmentation fault on maxdb_query in PHP | ||
---|---|---|---|
Submitted: | 1 Jun 2006 13:17 | Modified: | 22 Nov 2006 8:38 |
Reporter: | [ name withheld ] | Email Updates: | |
Status: | No Feedback | Impact on me: | |
Category: | MaxDB | Severity: | S1 (Critical) |
Version: | 7.6.00.27 | OS: | Linux (Linux) |
Assigned to: | CPU Architecture: | Any |
[1 Jun 2006 13:17]
[ name withheld ]
[1 Jun 2006 17:24]
C.J. Adams-Collier
Hey there! Can you start by giving me the query you are issuing? It would be great if you could create a very simple .php script to exercise the bug. Just enough to cause the segfault. Thanks! C.J.
[2 Jun 2006 11:38]
[ name withheld ]
Try to use maxdb_free_result 2 times and one of them should be in class destructor. For ex.: class A { private $res; function __destruct() { $this->do_something(); } function do_something() { if ($this->res) maxdb_free_result($res); } } $b = new A(); $b->do_something(); We fixed this by adding $this->res = null after maxdb_free_result();
[22 Oct 2006 8:38]
Valeriy Kravchuk
Please, try to repeat with a newer version, 7.6.00.34, and inform about the results.
[23 Nov 2006 0:00]
Bugs System
No feedback was provided for this bug for over a month, so it is being suspended automatically. If you are able to provide the information that was originally requested, please do so and change the status of the bug back to "Open".