alexcrichton opened Issue #1408:
Our fuzzers have caught an issue with debug information where a debug assert is getting tripped for an input wasm file (cc @yurydelendik).
This can be reproduced with:
$ cargo run -- -g testcase.watNote that debug assertions need to be enabled, which is the default in dev mode.
The test case has been slightly reduced with
creduce
, but it looks like it's not making tons of progress past what's already there.
alexcrichton labeled Issue #1408:
Our fuzzers have caught an issue with debug information where a debug assert is getting tripped for an input wasm file (cc @yurydelendik).
This can be reproduced with:
$ cargo run -- -g testcase.watNote that debug assertions need to be enabled, which is the default in dev mode.
The test case has been slightly reduced with
creduce
, but it looks like it's not making tons of progress past what's already there.
alexcrichton labeled Issue #1408:
Our fuzzers have caught an issue with debug information where a debug assert is getting tripped for an input wasm file (cc @yurydelendik).
This can be reproduced with:
$ cargo run -- -g testcase.watNote that debug assertions need to be enabled, which is the default in dev mode.
The test case has been slightly reduced with
creduce
, but it looks like it's not making tons of progress past what's already there.
alexcrichton closed Issue #1408:
Our fuzzers have caught an issue with debug information where a debug assert is getting tripped for an input wasm file (cc @yurydelendik).
This can be reproduced with:
$ cargo run -- -g testcase.watNote that debug assertions need to be enabled, which is the default in dev mode.
The test case has been slightly reduced with
creduce
, but it looks like it's not making tons of progress past what's already there.
Last updated: Nov 22 2024 at 17:03 UTC