Bug 29825 - Segfault in libaprutil-0.so.9.5
Summary: Segfault in libaprutil-0.so.9.5
Status: CLOSED DUPLICATE of bug 28086
Alias: None
Product: Apache httpd-2
Classification: Unclassified
Component: Core (show other bugs)
Version: 2.0.49
Hardware: PC other
: P3 critical (vote)
Target Milestone: ---
Assignee: Apache HTTPD Bugs Mailing List
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2004-06-27 12:12 UTC by Oliver Feiler
Modified: 2004-11-16 19:05 UTC (History)
0 users



Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Oliver Feiler 2004-06-27 12:12:17 UTC
I have encountered the following segfault on OpenBSD 3.5. I can't say what
caused it, it must have happened while running normally.

GNU gdb 4.16.1
Copyright 1996 Free Software Foundation, Inc.
GDB is free software, covered by the GNU General Public License, and you are
welcome to change it and/or distribute copies of it under certain conditions.
Type "show copying" to see the conditions.
There is absolutely no warranty for GDB.  Type "show warranty" for details.
This GDB was configured as "i386-unknown-openbsd3.5"...
(gdb) core-file httpd.core
Core was generated by `httpd'.
Program terminated with signal 11, Segmentation fault.
Reading symbols from /usr/local/apache2/lib/libaprutil-0.so.9.5...done.
Reading symbols from /usr/local/apache2/lib/libexpat.so.1.0...done.
Reading symbols from /usr/local/apache2/lib/libapr-0.so.9.5...done.
Reading symbols from /usr/lib/libm.so.1.0...done.
Reading symbols from /usr/lib/libpthread.so.2.4...done.
Reading symbols from /usr/lib/libc.so.30.3...done.
Reading symbols from /usr/libexec/ld.so...done.
Reading symbols from /usr/lib/libz.so.3.0...done.
Reading symbols from /usr/lib/libssl.so.8.0...done.
Reading symbols from /usr/lib/libcrypto.so.10.3...done.
Reading symbols from /usr/local/apache2/modules/libphp4.so...done.
Reading symbols from /usr/local/lib/libpq.so.3.1...done.
Reading symbols from /usr/local/lib/libmhash.so.2.0...done.
Reading symbols from /usr/local/lib/libmcrypt.so.8.5...done.
Reading symbols from /usr/local/lib/libltdl.so.1.2...done.
Reading symbols from /usr/local/lib/libpng.so.4.0...done.
Reading symbols from /usr/local/lib/libjpeg.so.62.0...done.
Reading symbols from /usr/local/lib/libcurl.so.2.2...done.
Reading symbols from /usr/local/lib/libbz2.so.10.2...done.
#0  0xe0e44c0 in ?? () from /usr/local/apache2/lib/libaprutil-0.so.9.5
(gdb) bt
#0  0xe0e44c0 in ?? () from /usr/local/apache2/lib/libaprutil-0.so.9.5
#1  0x1c077758 in regcomp (preg=0x3c09b4d0, pattern=0x3c09b4c8 "^\\.ht",
    cflags=0) at pcreposix.c:206
#2  0x1c063832 in ap_pregcomp (p=0x3c034018, pattern=0x3c09b4c8 "^\\.ht",
    cflags=0) at util.c:267
#3  0x1c07003d in filesection (cmd=0xcfbfa3e4, mconfig=0x3c07bd58,
    arg=0x3c09b4b9 "") at core.c:1765
#4  0x1c05d426 in invoke_cmd (cmd=0x3c01e2d4, parms=0xcfbfa3e4,
    mconfig=0x3c07bd58, args=0x3c07e190 "~ \"^\\.ht\">") at config.c:670
#5  0x1c05e15a in ap_walk_config_sub (current=0x3c07e170, parms=0xcfbfa3e4,
    section_vector=0x3c07ad10) at config.c:1048
#6  0x1c05e1e1 in ap_walk_config (current=0x3c07d338, parms=0xcfbfa3e4,
    section_vector=0x3c07ad10) at config.c:1087
#7  0x1c05f090 in ap_process_config_tree (s=0x3c0373b8, conftree=0x3c07d338,
    p=0x3c034018, ptemp=0x3c076018) at config.c:1621
#8  0x1c061ee2 in main (argc=3, argv=0xcfbfa500) at main.c:595
#9  0x1c01d441 in ___start ()
#10 0x1c01d3b7 in _start ()
#11 0xcfbfa670 in ?? ()
#12 0x9b4cd3c in ?? () from /usr/local/apache2/lib/libaprutil-0.so.9.5
Cannot access memory at address 0x9b4cd0e.
Comment 1 André Malo 2004-06-27 12:17:13 UTC
It looks more like the PHP bug. which PHP version? Did you restart the server
when this happened?
Comment 2 Oliver Feiler 2004-06-27 12:28:25 UTC
The core file's time stamp was not at a time where logcycle restarts the server
so it must have happened while running normally.

As you mention "the PHP bug", can you show me what you're referring to exactly
(bugzilla #, etc.)?

The backtrace doesn't really look like PHP was involved, though. At least to me.
PHP version was 4.3.6. This was the version the crash happened with. I've
upgraded to 5.0.0rc3 today as there are insane amounts of memory leaks. Didn't
help, but that is another issue. :/
Comment 3 André Malo 2004-06-27 12:40:52 UTC
Bug 28086.
Comment 4 Oliver Feiler 2004-06-27 12:56:00 UTC
Ok, certainly seems to be the same bug. PHP's bugzilla is f*cked at the moment,
but thanks for the pointer.

I'm closing this as a dup.

*** This bug has been marked as a duplicate of 28086 ***