You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hi, I ran buzzer with 20G RAM and OOM-killer problem occurred as mentioned in #58. When I increased the RAM to 40G, the problem still exists as below. I think there might be a memory leak in buzzer. Could you help me with this?
In addition, I used the -strategy=pointer_arithmetic which is tagged deprecated, and I didn't find any bugs. May I know which -strategy is more likely to find bugs?
That is indeed a lot of memory usage. There must be a leak somewhere, thanks for flagging it, I will dive more into it.
In terms of finding bugs: Right now we only have two strategies, pointer arithmetic or coverage guided. Although the as is state of buzzer will likely not find bugs as a lot of mitigations have been put in place in the verifier, you might need to implement new features or modify the strategies (or write your own strategy) to find something.
The idea with buzzer was not necessarily to have something that finds vulns out of the box but rather give you the tools and examples on how to play with ebpf and write fuzzing strategies/test cases that you think can catch certain types of bugs.
Hi, I ran buzzer with 20G RAM and OOM-killer problem occurred as mentioned in #58. When I increased the RAM to 40G, the problem still exists as below. I think there might be a memory leak in buzzer. Could you help me with this?
In addition, I used the
-strategy=pointer_arithmetic
which is tagged deprecated, and I didn't find any bugs. May I know which-strategy
is more likely to find bugs?The text was updated successfully, but these errors were encountered: