Re: [PHP4BETA] Segfault with large Apache
| From: | Dark Helmet | Date: | Tue, 04 Jan 2000 04:29:34 +0000 |
| Subject: | Re: [PHP4BETA] Segfault with large Apache | ||
| References: | 1 | Groups: | php.version4 |
| Request: | Send a blank email to php-version4+get-8893@lists.php.net to get a copy of this message | ||
On Tue, 4 Jan 2000, Sascha Schumann wrote:
>
> To get a useful backtrace, run
>
> $ gdb bin/httpd
> ...
> (gdb) r -X
> ...
> (gdb) bt
Blew right through my mind. :) gdb now reports a segfault in
pthread_mutex_lock:
Program received signal SIGSEGV, Segmentation fault.
0x411906ce in pthread_mutex_lock () from /lib/libpthread.so.0
(gdb) bt
#0 0x411906ce in pthread_mutex_lock () from /lib/libpthread.so.0
Cannot access memory at address 0x411906ce.
I noticed libpthread got pulled in earlier in the trace. I shouldn't need
this with Apache, right? Is it Oracle or db2? --enable-thread-safety fails
miserably on my system oddly enough.