rust/crates/syntax/fuzz/Cargo.toml


[package]
name = "syntax-fuzz"
version = "0.0.1"
authors = ["rust-analyzer developers"]
publish = false
edition = "2018"

[package.metadata]
cargo-fuzz = true

[dependencies]
syntax = { path = ".." }
text_edit = { path = "../../text_edit" }
libfuzzer-sys = { git = "https://github.com/rust-fuzz/libfuzzer-sys.git" }

# Prevent this from interfering with workspaces
[workspace]
members = ["."]

[[bin]]
name = "parser"
path = "fuzz_targets/parser.rs"

[[bin]]
name = "reparse"
path = "fuzz_targets/reparse.rs"
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 09:55:53 -05:00
			`[package]`
Rename ra_syntax -> syntax 2020-08-12 11:26:51 -05: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 09:55:53 -05:00			`version = "0.0.1"`
Fix typo in Cargo.toml authors Fixes typo introduced in #782 2019-02-11 02:20:04 -06: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 09:55:53 -05:00			`publish = false`
Refactor parser fuzz testing 2019-03-21 12:05:12 -05: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 09:55:53 -05:00
			`[package.metadata]`
			`cargo-fuzz = true`

Refactor parser fuzz testing 2019-03-21 12:05:12 -05:00			`[dependencies]`
Rename ra_syntax -> syntax 2020-08-12 11:26:51 -05:00			`syntax = { path = ".." }`
Rename ra_text_edit -> text_edit 2020-08-12 10:03:06 -05:00			`text_edit = { path = "../../text_edit" }`
Refactor parser fuzz testing 2019-03-21 12:05:12 -05: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 09:55:53 -05: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 12:06:48 -05:00
			`[[bin]]`
			`name = "reparse"`
			`path = "fuzz_targets/reparse.rs"`