On 07.04.17 17:27, Juha Heinanen wrote:
> Daniel-Constantin Mierla writes:
>> It was the parser setting the value of host part to "", not the
>> transformation, so the change had to be done in other file. Can you try
>> again with latest master?
> thanks for the fix. now the crash is gone.
Daniel-Constantin Mierla writes:
> It was the parser setting the value of host part to "", not the
> transformation, so the change had to be done in other file. Can you try
> again with latest master?
thanks for the fix. now the crash is gone. statements:
$var(test_uri) =
It was the parser setting the value of host part to "", not the
transformation, so the change had to be done in other file. Can you try
again with latest master?
Cheers,
Daniel
On 07.04.17 16:05, Juha Heinanen wrote:
> Daniel-Constantin Mierla writes:
>
>> Thanks, I just pushed a patch, can you
Thanks, I just pushed a patch, can you try it?
Cheers,
Daniel
On 07.04.17 15:32, Juha Heinanen wrote:
> Daniel-Constantin Mierla writes:
>
>> 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
Daniel-Constantin Mierla writes:
> 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.
this is debian jessie with GNU gdb (Debian 7.7.1+dfsg-5) 7.7.1.
> Anyhow, you can extract the code
Daniel-Constantin Mierla writes:
> 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 0x7f9d268703e0 in
Is it latest master? The line is matching an LM_ERR() with only static
string.
You should list the code, in gdb:
frame 0
list
Cheers,
Daniel
On 07.04.17 14:20, Juha Heinanen wrote:
> k 5.1 crashes when executing this:
>
> $var(test_uri) = "tel:+358447058060";
> xlog("L_INFO", "**
