25 Nov
2010
25 Nov
'10
6 a.m.
On 11/25/2010 12:07 PM, marius zbihlei wrote:
On 11/25/2010 12:00 PM, dotnetdub wrote:
Hello
I see that the interesting line is already in the first mail . Please
try this
readelf -S /path/to/topoh.so
You should have somethink like this
[Nr] Name Type Addr Off Size ES Flg
Lk Inf Al
[ 0] NULL 00000000 000000 000000 00
0 0 0
.....
[10] .init PROGBITS 00001914 001914 000030 00 AX
0 0 4
[11] .plt PROGBITS 00001944 001944 000430 04 AX
0 0 4
[12] .text PROGBITS 00001d80 001d80 008008 00 AX
0 0 16
Note the address of the .text segment (in my case is 0x00001d80)
Then
gdb /path/to/kamailio core.dump
in the gdb console load the topoh.so
add-symbol-file /path/to/topoh.so 0xb7004000 + 0x<offset of .text
segment found as above>
then check the value of the Instruction pointer IP (0xb70070d9) Still in
the gdb console
x/s 0xb70070d9
You will get an offset relative to a function where the crashed
happened. This would be very helpful so please share the finding. Also
do a info registers (in the gdb console) and paste the content of the
registers as well.
Marius
On 24 November 2010 07:10, Daniel-Constantin Mierla
<miconda(a)gmail.com <mailto:miconda@gmail.com>> wrote:
If you don't have the mask ip to your host ip (kamailio listening
ip) like Alex pointed, do you have a core dump from where you can
send the backtrace?
Cheers,
Daniel
Hi Alex/Daniel,
so THe IP of this SIP proxy is x.x.x.11 and I am using x.x.x.10 for
the Mask IP.
I see the coredump in the root of the server..
ls /core -lah
-rw------- 1 root root 134M 2010-11-20 19:48 /core
which is the date it crashed.
gdb /sbin/kamailio /core
This GDB was configured as "i486-linux-gnu"...
Cannot access memory at address 0xb75f3fb0
I am running gdb from debian repo on 5.04 maybe I need to compile gdb?
Hello,
No, the problem is with the coredump AFAIK. Try looking thru
/var/log/messages and dmesg for any indication of a coredump and the
module that generated it. Please email those lines as well.
Marius
Thanks
Brian