Re: Apache segfaults after Midgard 1.6.3 install

Sam Przyswa <samp-pAC44m+R7J2pwVsU+up1+gC/[email protected]>
Newsgroups gmane.comp.web.midgard.user
Message-ID <[email protected]>
X-MailScanner-Information Please contact the ISP for more information
X-Arial Concept-MailScanner: Found to be clean

Sam Przyswa a écrit :

> X-MailScanner-Information Please contact the ISP for more information
> X-Arial Concept-MailScanner: Found to be clean
>
> Sam Przyswa a écrit :
>
>> X-MailScanner-Information Please contact the ISP for more information
>> X-Arial Concept-MailScanner: Found to be clean
>>
>> Piotras a écrit :
>>
>>> Try to reproduce segfault.
>>>
>>> Link to gdb simple howto.
>>> http://www.midgard-project.org/community/development/debugging.html
>>>  
>>>
>>
>> After back to 2.4.27 kernel, load a gdb compiled Apache, gdb says:
>>
>> Program received signal SIGSEGV, Segmentation fault.
>> [Switching to Thread 16384 (LWP 1201)]
>> 0x40235ede in mallopt () from /lib/libc.so.6
>
>
>
> After upgraded libc6, recompile Midgard I got:
>
> Program received signal SIGSEGV, Segmentation fault.
> [Switching to Thread 16384 (LWP 19589)]
> 0x40235fb1 in _int_malloc () from /lib/libc.so.6
>
> With apache 1.3.33, PHP 4.3.4, Midgard 1.6.3, OpenSSL 0.9.7c, mod_perl 
> 1.29


...with the backtrace:

Program received signal SIGSEGV, Segmentation fault.
[Switching to Thread 16384 (LWP 1110)]
0x40235fb1 in _int_malloc () from /lib/libc.so.6
(gdb) backtrace
#0  0x40235fb1 in _int_malloc () from /lib/libc.so.6
#1  0x40234fb3 in malloc () from /lib/libc.so.6
#2  0x408c99be in my_malloc () from /usr/lib/libmysqlclient.so.14
#3  0x408ee579 in vio_new () from /usr/lib/libmysqlclient.so.14
#4  0x408ebe43 in mysql_real_connect () from /usr/lib/libmysqlclient.so.14
#5  0x408aa5dd in zm_info_mysql () from /usr/lib/php4/20020429/mysql.so
#6  0x408aa77d in zif_mysql_connect () from /usr/lib/php4/20020429/mysql.so
#7  0x40f85b93 in execute () from /usr/lib/apache/1.3/libphp4.so
#8  0x40f85d0a in execute () from /usr/lib/apache/1.3/libphp4.so
#9  0x40f85d0a in execute () from /usr/lib/apache/1.3/libphp4.so
#10 0x40f8a3e9 in execute () from /usr/lib/apache/1.3/libphp4.so
#11 0x40f8a3e9 in execute () from /usr/lib/apache/1.3/libphp4.so
#12 0x40f73fde in zend_execute_scripts () from 
/usr/lib/apache/1.3/libphp4.so
#13 0x40f4b7d5 in php_execute_script () from /usr/lib/apache/1.3/libphp4.so
#14 0x40f8c516 in apache_php_module_main () from 
/usr/lib/apache/1.3/libphp4.so
#15 0x40f8d12e in apache_php_module_main () from 
/usr/lib/apache/1.3/libphp4.so
#16 0x40f8d195 in apache_php_module_main () from 
/usr/lib/apache/1.3/libphp4.so
#17 0x080553c3 in ap_invoke_handler ()
#18 0x08068465 in ap_some_auth_required ()
#19 0x08068614 in ap_process_request ()
#20 0x08060bd2 in ap_child_terminate ()
#21 0x08060e9a in ap_child_terminate ()
#22 0x08060f10 in ap_child_terminate ()
#23 0x08061a9a in ap_child_terminate ()
#24 0x08061ff8 in main ()
(gdb)

Sam.



-- 
Ce message a été vérifié par MailScanner
pour des virus ou des polluriels et rien de
suspect n'a été trouvé.
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.