Suricata

It doesn't contain the requested info.

The following links are the output of the gdb :

http://pastebin.com/A6xH5dJU

http://pastebin.com/qr3AzG92

When I use the drop rules at https://github.com/EmergingThreats/et-luajit-scripts, some online movies or some downloads (but not all) will quit Suricata unexpectedly. When I remove all those rules, there is no unexpectedly quit of Suricata while watching online movies and download.

I also have some other lua rules enabled but they are working normally.

I think some bad written lua script/rules will quit Suricata unexpectedly. It may be bug of Suricata.

Is that a reproducible segfault or Suricata just quits unexpectedly ?

It is reproducible segfault when I download/update the same game on iPad Mini.

Which lua drop rules are those that you use more specifically? (there are 3 that I see there - luajit-drop.rules, dyndns-drop.rules, dyndns-http-alert-and-drop.rules)

Can you share the gdb info (after you enable debugging in Suri)?

It is luajit-drop.rules.

They are attached here.

Ok. so they are the same gdb output - I thought it was a new case.

Can you please upload the output of "thread apply all bt" as previously requested (I only see "bt" in the txt files)

How to do that? I am not familiar with gdb. Detail is required.

I have used the flag --enable-debug and the Suricata does not crash but the traffic flow is slowed down a lot. I think Suricata cannot handle timeout properly for a high speed traffic on very slow lua script that caused the Suricata quit unexpectedly. I disable all very slow speed lua scripts/rules to avoid the problem.

Yes - it affects performance.
Although if your after a useful core dump you should use "./configure CFLAGS="-ggdb -O0"

Is this still an issue?

Those lua rules are not in use at the moment and Suricata has been updated to 3.2. The lua rules problem may be caused by the bad coding by ET or something else. Anyway, the lua rules have been disabled. This thread can be closed. Thanks.