Closed Bug 1818639 Opened 3 years ago Closed 4 months ago

Improve error message for wasm out of bounds

Categories

(Core :: JavaScript: WebAssembly, enhancement, P3)

Firefox 110
enhancement

Tracking

()

RESOLVED INVALID

People

(Reporter: bvisness, Unassigned)

References

Details

Attachments

(1 external file)

Expected results:

When accessing wasm memory out of bounds, report the invalid address to the user in the error message. This may require signal handling to extract the invalid address from a system exception.

The attached patch extracts the bad address from macOS system exceptions. It doesn't yet handle any other platforms, nor does it actually update the error message.

Severity: -- → N/A
Priority: -- → P3
Status: UNCONFIRMED → NEW
Ever confirmed: true

We were recently talking about doing something like this, but I'm not sure if any of this old work is still relevant, nor if we have another bug now where this would be a better fit.

Flags: needinfo?(rhunt)

It looks like your patch contains most of the code needed to do this. It looks like it doesn't support multi-memory though. This is the right bug to track the work.

Flags: needinfo?(rhunt)
Assignee: nobody → bvisness
Status: NEW → ASSIGNED
See Also: → 2010315

Un-assigning because Ryan's work is likely to subsume it.

Assignee: bvisness → nobody
Status: ASSIGNED → NEW

Subsumed by bug 2042493.

Status: NEW → RESOLVED
Closed: 4 months ago
Resolution: --- → INVALID
See Also: → 2042493
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: