Open fosstrack opened 3 years ago
If I switch the order of the rules in the file, I don't get the error. Seems like a conflict between the 2 rules, but I cannot figure it out.
Running gdb on the core dump:
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
Python 3.8.5 (default, Sep 4 2020, 07:30:14)
[GCC 7.3.0] :: Anaconda, Inc. on linux
Type "help", "copyright", "credits" or "license" for more information.
>>> import crash1
[New Thread 0x7ffff6fd6700 (LWP 1314782)]
[New Thread 0x7ffff67d5700 (LWP 1314783)]
Thread 1 "python" received signal SIGSEGV, Segmentation fault.
0x00007ffff70dd3ad in reduceExpressionSequence (tree=0x555555a39050, state=0x555555a3d1a8, exprs=0x555555a4b978, operator=12,
messageObject=<optimized out>, context=<optimized out>, i=0x7fffffffa26a, targetProperty=0x7fffffffa290) at src/rules/events.c:616
616 currentExpression = &exprs->expressions[*i];
I have similar test cases that use sequences within rulesets that report the error at the exact same location (src/rules/events.c:616)