Mirrors/rust-analyzer
2
0
Fork 0
mirror of https://github.com/rust-lang/rust-analyzer synced 2024-12-26 13:03:31 +00:00
Code Issues Projects Releases Packages Wiki Activity
rust-analyzer/crates/syntax/fuzz/Cargo.toml

28 lines
510 B
TOML
Raw Normal View History

Add trivial fuzzer for parser As described in #61, fuzz testing some parts of this would be ~~fun~~ helpful. So, I started with the most trivial fuzzer I could think of: Put random stuff into File::parse and see what happens. To speed things up, I also did cp src/**/*.rs fuzz/corpus/parser/ in the `crates/libsyntax2/` directory (running the fuzzer once will generate the necessary directories).
2018-09-08 14:55:53 +00:00
[package]
Rename ra_syntax -> syntax
2020-08-12 16:26:51 +00:00
name = "syntax-fuzz"
Add trivial fuzzer for parser As described in #61, fuzz testing some parts of this would be ~~fun~~ helpful. So, I started with the most trivial fuzzer I could think of: Put random stuff into File::parse and see what happens. To speed things up, I also did cp src/**/*.rs fuzz/corpus/parser/ in the `crates/libsyntax2/` directory (running the fuzzer once will generate the necessary directories).
2018-09-08 14:55:53 +00:00
version = "0.0.1"
Fix typo in Cargo.toml authors Fixes typo introduced in #782
2019-02-11 08:20:04 +00:00
authors = ["rust-analyzer developers"]
Add trivial fuzzer for parser As described in #61, fuzz testing some parts of this would be ~~fun~~ helpful. So, I started with the most trivial fuzzer I could think of: Put random stuff into File::parse and see what happens. To speed things up, I also did cp src/**/*.rs fuzz/corpus/parser/ in the `crates/libsyntax2/` directory (running the fuzzer once will generate the necessary directories).
2018-09-08 14:55:53 +00:00
publish = false
Refactor parser fuzz testing
2019-03-21 17:05:12 +00:00
edition = "2018"
Add trivial fuzzer for parser As described in #61, fuzz testing some parts of this would be ~~fun~~ helpful. So, I started with the most trivial fuzzer I could think of: Put random stuff into File::parse and see what happens. To speed things up, I also did cp src/**/*.rs fuzz/corpus/parser/ in the `crates/libsyntax2/` directory (running the fuzzer once will generate the necessary directories).
2018-09-08 14:55:53 +00:00
[package.metadata]
cargo-fuzz = true
Refactor parser fuzz testing
2019-03-21 17:05:12 +00:00
[dependencies]
Rename ra_syntax -> syntax
2020-08-12 16:26:51 +00:00
syntax = { path = ".." }
Rename ra_text_edit -> text_edit
2020-08-12 15:03:06 +00:00
text_edit = { path = "../../text_edit" }
Refactor parser fuzz testing
2019-03-21 17:05:12 +00:00
libfuzzer-sys = { git = "https://github.com/rust-fuzz/libfuzzer-sys.git" }
Add trivial fuzzer for parser As described in #61, fuzz testing some parts of this would be ~~fun~~ helpful. So, I started with the most trivial fuzzer I could think of: Put random stuff into File::parse and see what happens. To speed things up, I also did cp src/**/*.rs fuzz/corpus/parser/ in the `crates/libsyntax2/` directory (running the fuzzer once will generate the necessary directories).
2018-09-08 14:55:53 +00:00
# Prevent this from interfering with workspaces
[workspace]
members = ["."]
[[bin]]
name = "parser"
path = "fuzz_targets/parser.rs"
Add fuzz test for reparsing
2019-03-21 17:06:48 +00:00
[[bin]]
name = "reparse"
path = "fuzz_targets/reparse.rs"
Reference in a new issue Copy permalink