php.net |  support |  documentation |  report a bug |  advanced search |  search howto |  statistics |  random bug |  login
Bug #13646 Bad SQL kills httpd child
Submitted: 2001-10-11 18:24 UTC Modified: 2001-12-19 03:23 UTC
From: ceo at l-i-e dot com Assigned:
Status: Closed Package: Sybase-ct (ctlib) related
PHP Version: 4.0.6 OS: Mandrake 8.0
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 !
Your email address:
MUST BE VALID
Solve the problem:
40 + 1 = ?
Subscribe to this entry?

 
 [2001-10-11 18:24 UTC] ceo at l-i-e dot com
./configure \
        --with-apxs=/usr/local/apache/bin/apxs \
        --with-mysql=/usr/local/mysql \
        --with-sybase-ct=/usr/local/freetds \
        --with-mssql \
        --without-gd \
        --with-jpeg-dir=/usr/local \
        --with-png-dir=/usr/local \
        --with-freetype-dir=/usr/local \
        --with-zlib

Apache 1.3.20
PHP 4.0.6
MS SQL 7.0:
Microsoft SQL Server 7.00 - 7.00.623 (Intel X86) Nov 27 
1998 22:20:07 Copyright (c) 1988-1998 Microsoft 
Corporation Standard Edition on Windows NT 5.0 (Build 
2195: Service Pack 2)

If my SQL is "bad" -- using non-existent table etc, I get 
a "lost connection" to server, and this in Apache 
error_log:

FATAL:  emalloc():  Unable to allocate -2147483648 bytes

Backtrace from, I think, this particular issue...

#0  _dl_lookup_versioned_symbol (undef_name=0x804bcec 
"kill", undef_map=0x40015a40, ref=0xbffff1ec,
    symbol_scope=0x40015b94, version=0x40025820, 
reloc_type=7, explicit=0) at do-lookup.h:80
80      do-lookup.h: No such file or directory.
---Type <return> to continue, or q <return> to quit---
        in do-lookup.h
(gdb) bt
#0  _dl_lookup_versioned_symbol (undef_name=0x804bcec 
"kill", undef_map=0x40015a40, ref=0xbffff1ec,
    symbol_scope=0x40015b94, version=0x40025820, 
reloc_type=7, explicit=0) at do-lookup.h:80
#1  0x4000d360 in fixup (l=0x40015a40, reloc_offset=976) 
at dl-runtime.c:89
#2  0x4000d510 in _dl_runtime_resolve () at 
dl-runtime.c:203
#3  0x400a5b68 in killpg () from /lib/libc.so.6
#4  0x4000d360 in fixup (l=0x80bc288, reloc_offset=976) at 
dl-runtime.c:89
#5  0x4000d510 in _dl_runtime_resolve () at 
dl-runtime.c:203
#6  0x0806175f in main ()
#7  0x400950de in __libc_start_main () from /lib/libc.so.6
(gdb)

Patches

Add a Patch

Pull Requests

Add a Pull Request

History

AllCommentsChangesGit/SVN commitsRelated reports
 [2001-12-18 13:43 UTC] lobbin@php.net
What lib is used? And can this be reproduced with latest version of PHP (4.1.0?)

See http://bugs.php.net/bugs-generating-backtrace.php for information about how to generate useful backtraces.

R.
 [2001-12-18 20:32 UTC] ceo at l-i-e dot com
>What lib is used?

Sybase ASE that was current as of 2001 OCT 11.

> And can this be reproduced with latest version of PHP 
>(4.1.0?)

I don't have access to the hardware/software any more. :-(

SORRY!!!

It *MAY* have just been their lying to me about which MS SQL 
Service Packs had been installed, too. :-|

I know I ended up spending over a week digging around for 
what else could be wrong after they said "Oh yes, we have 
all the latest service packs installed."  Not.

Not sure if this particular report was before or after that 
little scena
 
PHP Copyright © 2001-2021 The PHP Group
All rights reserved.
Last updated: Thu Mar 04 13:01:25 2021 UTC