[SR-Users] segfault in siptrace module using setflag?

[samuel]

The output of the requested command is:
(gdb) p *a
Cannot access memory at address 0x485f3832315f4d43

I'll try to load  the debugger module, and send the requested information
to digg into the problem.

Thanks again!
SAmuel.

On 9 October 2012 13:25, Daniel-Constantin Mierla <miconda at gmail.com> wrote:

> The line matches the access to the action, can you send also the output
> inside gdb for command:
>
> p *a
>
> Also, as I understand you can reproduce it, can you load debugger module,
> set its parameter cfg_trace to 1 and run again. Then send the lines printed
> by the cfg trace before the crash, so I can track what actions in the
> config were executed.
>
> Daniel
>
>
> On 10/9/12 1:01 PM, samuel wrote:
>
>> This is the output of the core file:
>>
>> (gdb) bt full
>> #0  do_action (h=<value optimized out>, a=0x485f3832315f4d43, msg=<value
>> optimized out>) at action.c:340
>>
>
> --
> Daniel-Constantin Mierla - http://www.asipto.com
> http://twitter.com/#!/miconda - http://www.linkedin.com/in/**miconda<http://www.linkedin.com/in/miconda>
> Kamailio Advanced Training, Berlin, Nov 5-8, 2012 -
> http://asipto.com/u/kat
> Kamailio Advanced Training, Miami, USA, Nov 12-14, 2012 -
> http://asipto.com/u/katu
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.sip-router.org/pipermail/sr-users/attachments/20121009/6f5da789/attachment.htm>