[Oisf-users] analyzing http parsing errors

Christophe Vandeplas christophe at vandeplas.com
Wed Dec 14 21:43:14 UTC 2011

On Wed, Dec 14, 2011 at 1:47 PM, Christophe Vandeplas
<christophe at vandeplas.com> wrote:
> Running that DEBUG enabled Suricata in gdb I get  (After a first breakpoint I 'continue'd )
> [3091] 14/12/2011 -- 11:39:33 - (tm-threads.c:1810) <Info> (TmThreadWaitOnThreadInit) -- all 5 packet processing threads, 3 management threads initialized, engine started.
> Program received signal EXC_BAD_ACCESS, Could not access memory.
> Reason: KERN_PROTECTION_FAILURE at address: 0x00000001029920f8
> [Switching to process 93462 thread 0x1a03]
> 0x00000001001b5205 in ?? ()

Ok, great, I found the problem of this SEGFAULT.
It was caused by compiler optimization doing incorrect things with a
pointer (it removed it).

Forcing -O0 everywhere got me a working suricata binary with debugging
symbols and output.

Now I can start troubleshooting the http parsing errors.

More information about the Oisf-users mailing list