25 Feb
2019
25 Feb
'19
12:36 p.m.
Today there was another report with a backtrace like the one you
reported, so I try to figure out if there are any common aspects between
the two systems.
Can you tell what linux distro and version was running in your case?
Also, can you give the output for:
uname -a
Cheers,
Daniel
On 14.02.19 08:54, Juha Heinanen wrote:
Daniel-Constantin Mierla writes:
--
Daniel-Constantin Mierla -- www.asipto.com
www.twitter.com/miconda -- www.linkedin.com/in/miconda
Kamailio World Conference - May 6-8, 2019 -- www.kamailioworld.com
Kamailio Advanced Training - Mar 4-6, 2019 in Berlin; Mar 25-27, 2019, in Washington, DC,
USA -- www.asipto.com
However, that had invalid access to transaction
pointer. In this case,
accessing transaction is ok, by setting a variable to the address of one
of its fields, but then the variable becomes NULL, which is not possible
unless the stack got corrupted/overwritten. However, from the moment of
setting the variable till the moment of the crash, there are no other
set or copy operations, therefore nothing that I can relate to
kamailio's c code. Maybe it happens another time and the backtrace will
be different.
I agree, Juha