ID:               45005
 Updated by:       [EMAIL PROTECTED]
 Reported By:      deusmax at gmail dot com
-Status:           Open
+Status:           Bogus
 Bug Type:         PostgreSQL related
 Operating System: ubuntu linux gutsy
 PHP Version:      5.2CVS-2008-05-15 (CVS)
 New Comment:

See above.


Previous Comments:
------------------------------------------------------------------------

[2008-07-30 19:54:59] bugs dot php dot net at zetafleet dot com

This is a duplicate of Bug #40926.

------------------------------------------------------------------------

[2008-05-15 12:28:33] deusmax at gmail dot com

Here is a backtrace:

(gdb) bt
#0  0xb6412ea0 in ?? ()
#1  0xb7870705 in CRYPTO_lock () from
/usr/lib/i686/cmov/libcrypto.so.0.9.8
#2  0xb78dc5ad in ?? () from /usr/lib/i686/cmov/libcrypto.so.0.9.8
#3  0x00000009 in ?? ()
#4  0x00000001 in ?? ()
#5  0xb79562bb in ?? () from /usr/lib/i686/cmov/libcrypto.so.0.9.8
#6  0x00000161 in ?? ()
#7  0xb79669b8 in ?? () from /usr/lib/i686/cmov/libcrypto.so.0.9.8
#8  0x085df8b8 in ?? ()
#9  0xbfdaa978 in ?? ()
#10 0xb78dddda in ERR_free_strings ()
   from /usr/lib/i686/cmov/libcrypto.so.0.9.8
Backtrace stopped: frame did not save the PC
(gdb)

My php5 binary doesn't have debug symbols enabled, it seems.
Anyway, I ran the code again from within the debuger and got this
output:

bash%gdb /usr/bin/php5 

This GDB was configured as "i486-linux-gnu"...
(no debugging symbols found)
Using host libthread_db library
"/lib/tls/i686/cmov/libthread_db.so.1".
(gdb) run /home/dias/tmp/test.php
Starting program: /usr/bin/php5 /home/dias/tmp/test.php
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
---Type <return> to continue, or q <return> to quit---
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread -1215936848 (LWP 29629)]
Error while reading shared library symbols:
Cannot find new threads: generic error
Inserting array... Done
Closed

Program received signal SIGSEGV, Segmentation fault.
[Switching to Thread -1215936848 (LWP 29629)]
0xb644fea0 in ?? ()
(gdb) bt
#0  0xb644fea0 in ?? ()
#1  0xb78ad705 in CRYPTO_lock () from
/usr/lib/i686/cmov/libcrypto.so.0.9.8
#2  0xb79195ad in ?? () from /usr/lib/i686/cmov/libcrypto.so.0.9.8
#3  0x00000009 in ?? ()
#4  0x00000001 in ?? ()
#5  0xb79932bb in ?? () from /usr/lib/i686/cmov/libcrypto.so.0.9.8
#6  0x00000161 in ?? ()
#7  0xb79a39b8 in ?? () from /usr/lib/i686/cmov/libcrypto.so.0.9.8
#8  0x085df8b8 in ?? ()
#9  0xbf837c08 in ?? ()
#10 0xb791adda in ERR_free_strings ()
   from /usr/lib/i686/cmov/libcrypto.so.0.9.8
Backtrace stopped: frame did not save the PC
(gdb)

------------------------------------------------------------------------

[2008-05-15 11:53:44] deusmax at gmail dot com

Description:
------------
when using pg_insert(),everything works, but when the program
terminates it reports a "Segmentation fault".

Data are properly inserted into table,
db connection closed ok. too.

create a small table

create table test (regn text, mtow numeric(6,2), tonbl timestamp(0)
with time zone);

Actually, just using pg_convert() on the array causes the same
segmentation fault to be reported. Without even trying to insert the
data.

Reproduce code:
---------------
Use some data
$data = array('regn' => 'defi', 
              'mtow' =>  23.2,
              'tonbl' => '2008-05-15T16:15:16+00');

insert using:
$db = pg_connect("dbname=foo");
$res = pg_insert($db, 'test', $data);
pg_close($db);




------------------------------------------------------------------------


-- 
Edit this bug report at http://bugs.php.net/?id=45005&edit=1

Reply via email to