-
Notifications
You must be signed in to change notification settings - Fork 29
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
casr-libfuzzer for Rust programs. #143
Comments
Oh I didn't notice this is already done in another PR #132 😅 |
Ah, actually maybe it's not really done in #132..? |
Hi! Thanks for the kind words! We are happy that you find Lines 13 to 14 in c50d011
In the output you provided there are Rust backtrace and libFuzzer's stacktrace. What if we take to account only Rust backtrace for deduplication in such case? I suppose that in much more cases Rust backtrace has more information than libfuzzer's stacktrace. What do you think? This way we analyze crashes from go-fuzz. |
Oh, the PR's name is a little bit confusing:). In this PR I add fuzz targets for stacktrace parsers to have some fuzzing in CI. |
Yes sounds good to me 👍 |
Hi all 👋
First, thanks for creating this project. I'm using casr-libfuzzer and it's very useful for deduplication.
I want to ask if it's possible to further extend casr's crash dedup & clustering algorithm for Rust programs.
When you run Rust programs (instrumented with cargo fuzz), the output will have two parts.
One is the backtrace from liffuzzer, the other is the Rust's backtrace.
For example ↓:
The first part is the backtrace from Rust, the second is from libfuzzer.
Now the idea is when fuzzing Rust targets the Rust's backtrace would also be useful for deduplicating the crashes.
I read the clustering & distance-calculating algorithm in the casr paper
and I think we could potentially,
similarity_metric_rust
with the metric computed using libfuzzer's bactrace and do the clustring.Do you think it would be a good idea and it's doable to apply the same algorithm for the backtrace of Rust?
The text was updated successfully, but these errors were encountered: