You are viewing a plain text version of this content. The canonical link for it is here.
Posted to modules-dev@httpd.apache.org by wangyz <wa...@tongtech.com> on 2008/06/25 07:56:04 UTC
Re: [可能是垃圾邮件] Re: how to catch segment fault
Kevac Marko wrote:
> Try the same you were doing, but build Apache with "-g".
>
> CCFLAGS="-g" ./configure && make && make install
>
> On Wed, Jun 25, 2008 at 5:44 AM, langwnwk <la...@gmail.com> wrote:
>
>> Eric Covener wrote:
>>
>>> On Tue, Jun 24, 2008 at 4:39 AM, langwnwk <la...@gmail.com> wrote:
>>>
>>>
>>>> We had developed a clustering and loadbalancing module on apache. when
>>>> we made benchmark test.
>>>> I often find segments fault in error_log,such this
>>>> [notice] child pid 25600 exit signal Segmentation fault (11).
>>>> but this module run well.
>>>>
>>>>
>>> Set CoreDumpDirectory in httpd.conf and check ulimit -c; you may need
>>> to change your startup script for the latter.
>>> --
>>> Eric Covener
>>> covener@gmail.com
>>>
>>>
>>>
>> thanks your answer. I had set CoreDumpDirector and run command " ulimit -c
>> unlimited" .then startup server using this command " apachect1 start "
>> but no any core file still.
>> you said, maybe i will change the startup script. can you tell me how to
>> change startup script
>>
>>
>>
>
>
>
>
hi Kevac Marko
I had check config_var.mk file .in this file EXTRA_CFLAGS had
been set -g.
by the way. I think "-g" is only gcc flag for builiding a debug version.
it has no relation to core file.
Re: [可能是垃圾邮件] Re: [可能是垃圾邮件] Re: how to catch segment fault
Posted by langwnwk <la...@gmail.com>.
Kevac Marko wrote:
> Yes, but it allows you to debug your module with gdb (with or without
> core file) with ease.
>
> Run gdb bin/httpd, print 'r -X'.
> It will start Apache in single mode (with one process).
> Than load server somehow and wait for gdb to catch sigfault. It will
> show you precise line of code where sigfault occurred.
>
> On Wed, Jun 25, 2008 at 9:56 AM, wangyz <wa...@tongtech.com> wrote:
>
>> thanks your answer. I had set CoreDumpDirector and run command " ulimit
>> -c
>> unlimited" .then startup server using this command " apachect1 start "
>> but no any core file still.
>> you said, maybe i will change the startup script. can you tell me how to
>> change startup script
>>
>
>
thanks . I understand. I will try as you said.
Re: [可能是垃圾邮件] Re: how to catch segment fault
Posted by Kevac Marko <mk...@gmail.com>.
Yes, but it allows you to debug your module with gdb (with or without
core file) with ease.
Run gdb bin/httpd, print 'r -X'.
It will start Apache in single mode (with one process).
Than load server somehow and wait for gdb to catch sigfault. It will
show you precise line of code where sigfault occurred.
On Wed, Jun 25, 2008 at 9:56 AM, wangyz <wa...@tongtech.com> wrote:
> thanks your answer. I had set CoreDumpDirector and run command " ulimit
> -c
> unlimited" .then startup server using this command " apachect1 start "
> but no any core file still.
> you said, maybe i will change the startup script. can you tell me how to
> change startup script
--
С уважением, Кевац Марко
Sincerely yours, Kevac Marko