The issue was with previous fragment (misread the log message in the
first place). But was easy to spot what could be the previous fragment
and I think I fixed with commit:
-
If you can give it a try, then it can be backported (I had no option to
try it here for now).
Cheers,
Daniel
On 15/05/14 06:51, Juha Heinanen wrote:
Daniel-Constantin Mierla writes:
What version are you using?
this is
version 4.1 taken from git on may 12.
It looks like a buffer overflow somewhere. Can
you give the output of
next commands in gdb:
frame 3
p *f
i got this:
(gdb) frame 3
#3 0x08179f86 in qm_debug_frag (qm=0xb6dea008, f=0xb70f6a64)
at mem/q_malloc.c:161
161 mem/q_malloc.c: No such file or directory.
(gdb) p *f
$1 = {size = 60, u = {nxt_free = 0xb6dea32c, is_free = -1226923220},
file = 0xb1b6ea2f "siputils: checks.c",
func = 0x823e2a3 "fragm. from qm_malloc", line = 383, check = 4042322160}
-- juha