Actions
Bug #1981
closedluajit states fail to run with valgrind
Affected Versions:
Effort:
Difficulty:
Label:
Description
A regular run completes :
/opt/suricata-git-rctests/bin/suricata -c /home/pmanev/sandnet-qa/test/asan-ginfiz-runs/fuzz.suricata.sandnet.socket.yaml -r /home/pmanev/sandnet-qa/test/asan-ginfiz-runs/logs-weekly//2000032.pcap-fuzz-2016-12-11-04-46-32 -l /home/pmanev/sandnet-qa/test/asan-ginfiz-runs/logs-weekly// -s /opt/suricata-git-rctests/etc/suricata/rules/events-allenabled.rules[2369] 11/12/2016 -- 04:58:41 - (suricata.c:1007) <Notice> (SCPrintVersion) -- This is Suricata version 3.2dev (rev 94bc7e5) [2369] 11/12/2016 -- 04:59:01 - (tm-threads.c:2098) <Notice> (TmThreadWaitOnThreadInit) -- all 13 packet processing threads, 2 management threads initialized, engine started. [2369] 11/12/2016 -- 04:59:01 - (suricata.c:2630) <Notice> (main) -- Signal Received. Stopping engine. [2451] 11/12/2016 -- 04:59:01 - (source-pcap-file.c:388) <Notice> (ReceivePcapFileThreadExitStats) -- Pcap-file module read 10148 packets, 2293305 bytes
If valgrind is added (using the same settings) - it fails to start (even after increasing "luajit.states" quite a bit in yaml)
valgrind -v --log-file=/home/pmanev/sandnet-qa/test/asan-ginfiz-runs/logs-weekly//2000032.pcap-fuzz-2016-12-11-04-46-322016-12-11-04-46-32-memcheck-vg.log /opt/suricata-git-rctests/bin/suricata -c /home/pmanev/sandnet-qa/test/asan-ginfiz-runs/fuzz.suricata.sandnet.socket.yaml -r /home/pmanev/sandnet-qa/test/asan-ginfiz-runs/logs-weekly//2000032.pcap-fuzz-2016-12-11-04-46-32 -l /home/pmanev/sandnet-qa/test/asan-ginfiz-runs/logs-weekly// -s /opt/suricata-git-rctests/etc/suricata/rules/events-allenabled.rules [2466] 11/12/2016 -- 04:59:36 - (suricata.c:1007) <Notice> (SCPrintVersion) -- This is Suricata version 3.2dev (rev 94bc7e5) [2466] 11/12/2016 -- 04:59:36 - (util-pool.c:169) <Error> (PoolInit) -- [ERRCODE: SC_ERR_POOL_INIT(66)] - alloc error [2466] 11/12/2016 -- 04:59:36 - (util-luajit.c:93) <Error> (LuajitSetupStatesPool) -- [ERRCODE: SC_ERR_LUA_ERROR(212)] - luastate pool init failed, lua/luajit keywords won't work
Updated by Victor Julien about 8 years ago
- Priority changed from Normal to Low
Valgrind does memory tricks and luajit does memory tricks. Not surprised there are issues.
Updated by Victor Julien almost 8 years ago
- Target version set to TBD
Don't think this is worth spending time on.
Actions