Tzafrir Cohen schrieb:
> On Fri, Oct 24, 2008 at 07:09:57PM +0200, thomas schorpp wrote:
>> thomas schorpp schrieb:
>>> thomas schorpp schrieb:
>>>> thomas schorpp schrieb:
>>>>> Program received signal SIGSEGV, Segmentation fault.
>>>>> [Switching to Thread 0xb5f05b90 (LWP 27978)]
>>>>> 0xb7a1bf49 in span_log_set_message_handler () from
>>>>> /usr/lib/libspandsp.so.1
>>>>> (gdb) bt
>>>>> #0 0xb7a1bf49 in span_log_set_message_handler () from
>>>>> /usr/lib/libspandsp.so.1
>>>>> #1 0xb5fb5289 in ?? () from /usr/lib/callweaver/modules/app_txfax.so
>>>>> #2 0x00010d04 in ?? ()
>>>>> #3 0xb5fb4800 in ?? () from /usr/lib/callweaver/modules/app_txfax.so
>>>>> #4 0xb5fb4860 in ?? () from /usr/lib/callweaver/modules/app_txfax.so
>>>>> #5 0x09ea9528 in ?? ()
>>>>> #6 0xb5fb65ca in ?? () from /usr/lib/callweaver/modules/app_txfax.so
>>>>> #7 0x00000000 in ?? ()
>>>>> (gdb)
>>>>> reproducible. doing debug build next days.
>>>>>
>>>>> y
>>>>> tom
>>>>>
>>>> fixed in rel 1.2 SVN rev. 5210 :)
>>>>
>>>> someone who is liked by retrospectiva pls close the tickets in
>>>> bugtracker.
>>>>
>>>> y
>>>> tom
>>>>
>>> new segfault occured today:
>>>
>>> tom3:~# grep segfault /var/log/syslog
>>> Oct 23 14:48:30 tom3 kernel: callweaver[2666]: segfault at 65768e39 eip
>>> b7eb8fda esp b65ad230 error 4
>>> tom3:~#
>>> Oct 23 14:46:12 VERBOSE[3052669840] logger.c: == Spawn extension
>>> (von-sipgate-de, talk, 3) exited non-zero on 'SIP/xxxxxxx$
>>> Oct 23 14:46:12 VERBOSE[3052669840] logger.c: -- Executing
>>> [EMAIL PROTECTED]:1] Hangup("SIP/xxxxxx-8669", "")
>>> Oct 23 14:46:12 VERBOSE[3052669840] logger.c: == Spawn extension
>>> (von-sipgate-de, h, 1) exited non-zero on 'SIP/xxxxxxx-86$
>>> Oct 23 14:48:15 NOTICE[3059424144] chan_sip.c: Unknown SIP command
>>> 'PUBLISH' from '192.168.0.xxx'
>>>
>>> activated coredump now:
>>> root 5306 1 0 15:32 pts/0 00:00:00 /bin/sh
>>> /usr/sbin/safe_callweaver -p
>>> 129 5310 5306 0 15:32 pts/0 00:00:15 /usr/sbin/callweaver -p
>>> -vvvg -f
>>>
>>> where will the coredump be dropped? /tmp ?
>>>
>>> will a -O0 -g3 build run fast enough on a P2 266 or is -O2 -g sufficent
>>> for stack dumps with source code info?
>>>
>>> now waiting for the milkpot to cook.
>>>
>>> y
>>> tom
>>>
>> reproducible:
>>
>> tom3:~# grep callweaver /var/log/syslog
>> Oct 24 14:31:29 tom3 callweaver[5310]: WARNING[3060173712]: chan_sip.c:12541
>> in handle_response_register: Got 200 OK on REGISTER that isn't a register
>> Oct 24 15:45:54 tom3 kernel: callweaver[5324]: segfault at 61666560 eip
>> b7bf815c esp b6664218 error 4
>> Oct 24 15:45:54 tom3 logger: callweaver: CallWeaver ended with exit status
>> 139
>> Oct 24 15:45:55 tom3 logger: callweaver: CallWeaver exited on signal 11.
>> Oct 24 15:45:55 tom3 logger: callweaver: Found and moved core dumps to
>> /var/lib/callweaver/core/2008-10-24-15:45:55
>> Oct 24 15:45:55 tom3 logger: callweaver: Automatically restarting CallWeaver.
>>
>> coredump is pretty worthless without debug info:
>> (no debugging symbols found)
>
> Does the callweaver binary have debug information or is it stripped?
dh_strip
>
> If you use debs, use a -dbg package.
current debian/ scripts included do not build one.
>
> If you do have debug information, make sure you give it the name of the
> binary:
>
> gdb -c path/to/core_file path/to/callweaver
>
makes no difference. is it sufficent to #dh_strip in debian/rules when gcc -O2
-g ?
y
tom
_______________________________________________
Callweaver-dev mailing list
[email protected]
http://lists.callweaver.org/mailman/listinfo/callweaver-dev
