Re: PHP core dump with openlink odbc drivers

Your crash seems to be associated with SQLAllocConnect, one would only expect this to be called once near the start of the processing - at odbc_connect (). When you make multiple queries are you making multiple connections (with associated disconnects)? I realise this is unlikely, but it is worth knowing when looking for possible problems.... What would be useful to know is: * are all your queries on the same connection handle? * are all your queries on the same statement handle? Steve Erik Andrejko wrote: > > I am having a little trouble with PHP 3.0.6. > > The php scripts that do not access the odbc datasource never have a problem, however the php > scripts that do access the odbc datasource do crash proportionately to the number of queries that > are executed in the script. (i.e. a script that performs ~ 100 queries has never loaded, but a > script that performs 4 queries usually loads). > > Other applications that use the same odbc drivers have never crashed as php does. > > Here is the dump: > > (gdb) run -X > Starting program: /usr/local/apache/bin/httpd -X > (no debugging symbols found)...(no debugging symbols found)... > (no debugging symbols found)... > Program received signal SIGSEGV, Segmentation fault. > 0x400d2698 in chunk_free (ar_ptr=0x401268a0, p=0x816f750) at malloc.c:2937 > malloc.c:2937: No such file or directory. > (gdb) bt > #0 0x400d2698 in chunk_free (ar_ptr=0x401268a0, p=0x816f750) at malloc.c:2937 > #1 0x400d1daa in malloc_extend_top (ar_ptr=0x401268a0, nb=88) at malloc.c:2459 > #2 0x400d23f5 in chunk_alloc (ar_ptr=0x401268a0, nb=88) at malloc.c:2788 > #3 0x400d1e85 in __libc_malloc (bytes=80) at malloc.c:2556 > #4 0x400114bb in SQLAllocConnect () -- Steve Williams Interactive Media & Tools Group Empress Software Inc. http://www.empress.com -- PHP Development Mailing List http://www.php.net/ To unsubscribe send an empty message to php-dev-unsubscribe@lists.php.net For help: php-dev-help@lists.php.net