We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Issue #42 was about a panic in residue_packet_read_partition but after fixing it, one of the samples now triggers a second allocator based error.
residue_packet_read_partition
You'd get an error like:
fatal runtime error: allocator memory exhausted
And then a segfault.
The text was updated successfully, but these errors were encountered:
Nice, even gdb segfaults when I'm trying to study the error.
Sorry, something went wrong.
Hmm, with Rust stable there is no gdb segfault.
Backtrace points to the error originating in lewton::header::read_header_comment (packet=...) at src/header.rs:329.
lewton::header::read_header_comment (packet=...) at src/header.rs:329
Yeah it seems it wants 1979711488 many comments. Quite a number!
Oh, I have a whole bunch of OOM-crashing samples from fuzzer. Here you go: oom-samples.zip
No branches or pull requests
Issue #42 was about a panic in
residue_packet_read_partition
but after fixing it, one of the samples now triggers a second allocator based error.You'd get an error like:
And then a segfault.
The text was updated successfully, but these errors were encountered: