[Kamailio-Users] crash/offset exceeds message size

Iñaki Baz Castillo ibc at aliax.net
Fri Jun 5 10:58:13 CEST 2009


2009/6/5 Aymeric Moizard <jack at atosc.org>:
>
> Hi Again, (sorry for wrong subject previous post),
>
> I'm sure this is not enough to help, but I just got a crash using kamailio
> 1.5.
>
> Jun  5 10:24:43 ns26829 /usr/sbin/kamailio[29050]:
> CRITICAL:core:anchor_lump: offset exceeds message size (682 > 675)
> aborting...
> Jun  5 10:24:43 ns26829 /usr/sbin/kamailio[29127]: CRITICAL:core:receive_fd:
> EOF on 21
> Jun  5 10:24:43 ns26829 /usr/sbin/kamailio[29036]: INFO:core:handle_sigs:
> child process 29050 exited by a signal 6
> Jun  5 10:24:43 ns26829 /usr/sbin/kamailio[29036]: INFO:core:handle_sigs:
> core was not generated
> Jun  5 10:24:43 ns26829 /usr/sbin/kamailio[29036]: INFO:core:handle_sigs:
> terminating due to SIGCHLD
>
> What is that "offset exceeds message size"? What kind of trace should I take
> if this happen again?

Please, configure your system and Kamailio to generate verbose coredump.

Such a message occurred some time ago in ALL OpenSer/Kamailio versions
due when the "Content-Length" header value was greater than the real
body size, and a body modification was performed (as force_rtpproxy).
The bug was that the code used the "Content-Length" header value
instead of the real body size, so a segmentfault occurred due to wrong
memory access.

This could be a similar issue, please generate a coredump. Regards.


-- 
Iñaki Baz Castillo
<ibc at aliax.net>




More information about the sr-users mailing list