Hey there, We often run other peoples rules, and at times when we scan larger files we get "internal error: 30" which indicates that yara matched too many strings and basically ran out of room.
The question that naturally follows is "which string in which rule caused the problem?" That's hard to figure out because the files we load often have dozens of rules with lots of strings. It would be helpful if there was an option that listed the top N strings in order of how many times they matched (and what rule they're in), in descending order. Does this functionality exist in other ways? If not, then could someone point me in what areas of the source code I need to look at to accomplish this? Would anyone else find this useful? -- John W. Davison [email protected] -- You received this message because you are subscribed to the Google Groups "YARA" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
