(unknown charset) Re: Crashes with Grsecurity kernel

From: (unknown charset) Claus Assmann <ml+opendkim-users_at_esmtp.org>
Date: Sun, 11 Jan 2015 10:28:14 -0800

On Sun, Jan 11, 2015, Christian Rö�ner wrote:

> #0 0x00007f4250e3a825 in raise () from /lib64/libc.so.6
> #1 0x00007f4250e3bca8 in abort () from /lib64/libc.so.6
> #2 0x00007f4250e7ae22 in ?? () from /lib64/libc.so.6
> #3 0x00007f4250e809e6 in ?? () from /lib64/libc.so.6
> #4 0x00007f4253227f34 in mi_engine (ctx=ctx_at_entry=0x7f4254340300) at engine.c:409

Maybe you can take a look at the code and the data?
Depending on your version, this might be a free(buf) statement.
I don't know what kind of memory debugging support your OS offers,
but linking against an appropriate malloc library or setting
the proper options (or using valgrind?) might help to figure out
what's going on.
Received on Sun Jan 11 2015 - 18:28:26 PST