7 Apr
2017
7 Apr
'17
3:53 p.m.
What OS do you have and which version of gdb? The list command should
list the code around the line where the crash happens, but it doesn't do
it for you.
Anyhow, you can extract the code around src/modules/pv/pv_core.c:2243
and send it here, to be sure it is the one you use at the time of crash.
Daniel
On 07.04.17 14:40, Juha Heinanen wrote:
Daniel-Constantin Mierla writes:
--
Daniel-Constantin Mierla
www.twitter.com/miconda -- www.linkedin.com/in/miconda
Kamailio Advanced Training - May 22-24 (USA) - www.asipto.com
Kamailio World Conference - May 8-10, 2017 - www.kamailioworld.com
Is it latest master? The line is matching an
LM_ERR() with only static
string.
master as it was on april 3.
You should list the code, in gdb:
frame 0
list
Program terminated with signal SIGSEGV, Segmentation fault.
#0 0x00007f9d268703e0 in pv_set_ruri_host (msg=0x7f9d33607090,
param=0x7f9d32ca42c0, op=254, val=0x7ffe1d5bcfc0) at pv_core.c:2243
2243 pv_core.c: No such file or directory.
(gdb) frame 0
#0 0x00007f9d268703e0 in pv_set_ruri_host (msg=0x7f9d33607090,
param=0x7f9d32ca42c0, op=254, val=0x7ffe1d5bcfc0) at pv_core.c:2243
2243 in pv_core.c
(gdb) list
2238 in pv_core.c
-- juha