Skip to content

Conversation

@kripken
Copy link
Member

@kripken kripken commented Feb 10, 2026

These functions receive a reference value. We cannot log their
internals, but we can try to do some operations on them, and
this gets more such values moving across the JS/wasm
boundary. Future fuzzing of configureAll will build on this.

To achieve this, the logValue method had to be moved up in
the fuzzer, so we can use it from another place. The only
change there is to make it stop printing newlines all the time
(and let the caller do it, if needed).

@kripken kripken requested a review from tlively February 10, 2026 23:41
from the random input. Please report it with
seed: %(seed)d
seed: {seed}
Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

drive-by fix: this was not logging the number before.

Comment on lines 45 to 47
// - funcref cannot be logged because referenced functions can be inlined or
// removed during optimization
// - there's no point in logging anyref because it is opaque
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks like this comment needs updating.

loggableTypes.push_back(Type(HeapType::cont, Nullable));
}
if (wasm.features.hasExceptionHandling()) {
loggableTypes.push_back(Type(HeapType::exn, Nullable));
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I don't think exnref values can flow out to JS, so I don't think it makes sense to try to log them.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants