issues
search
trailofbits
/
ruzzy
A coverage-guided fuzzer for pure Ruby code and Ruby C extensions
GNU Affero General Public License v3.0
69
stars
3
forks
source link
issues
Newest
Newest
Most commented
Recently updated
Oldest
Least commented
Least recently updated
Add tests for `case` statements and other `===` usage
#21
mschwager
opened
2 months ago
0
Harness ends with DEADLYSIGNAL at start
#20
AdvenamTacet
opened
3 months ago
1
Create LeakSanitizer suppression rules to run with detect_leaks=1
#19
disconnect3d
opened
3 months ago
0
Add automated tests for LLVM 15-18
#18
mschwager
closed
3 months ago
0
Consider using __asan_default_options instead of ASAN_OPTIONS
#17
mschwager
opened
3 months ago
1
Support RUBY_VERSION and LLVM_VERSION build args when building Docker dev image
#16
mschwager
closed
3 months ago
0
Fix #14, support for Ruby back to 3.0.0
#15
mschwager
closed
3 months ago
0
Ruby 3.0 does not include Coverage.setup
#14
mschwager
closed
3 months ago
0
Bump LLVM version to 18
#13
AdvenamTacet
closed
3 months ago
1
Use apt clang instead of manually installing clang
#12
mschwager
closed
4 months ago
0
Add support for fuzzing pure Ruby code on Mac
#11
mschwager
opened
4 months ago
0
Add tests for real fuzzing runs
#10
mschwager
closed
4 months ago
0
Request Ruby C API make hooking coverage events publicly available
#9
mschwager
opened
4 months ago
3
Fix #7, add coverage support for Ruby code
#8
mschwager
closed
4 months ago
0
Add coverage support for Ruby code, not just C extensions
#7
mschwager
closed
4 months ago
2
Add support for FuzzedDataProvider
#6
mschwager
opened
5 months ago
1
Add support for UBSAN
#5
mschwager
closed
4 months ago
0
AddressSanitizer: CHECK failed: `((ptr[0] == kCurrentStackFrameMagic)) != (0)`
#4
mschwager
opened
5 months ago
3
Add CI for building and testing
#3
mschwager
closed
5 months ago
1
Fuzzing candidates
#2
mschwager
opened
5 months ago
6
Figure out how to compile `cruzzy` as part of the `gem install` process
#1
mschwager
closed
5 months ago
1