• Clemens Backes's avatar
    [wasm] Fix code offset after module cache hit · c6c86944
    Clemens Backes authored
    If the module cache was hit, we didn't set the code offset in the
    decoded module. Hence it was reported as 0 to the DevTools frontend,
    leading to subsequent errors.
    Note that this error can only happen if multiple isolates share the same
    module, which we cannot easily test in v8. Sharing within a single
    isolate is implemented via the script cache, so we won't report another
    script via CDP.
    
    R=thibaudm@chromium.org
    
    Bug: chromium:1114143
    Change-Id: I3218a3b12cf5be09d685e3f371f858ab799cef80
    Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/2519560Reviewed-by: 's avatarThibaud Michaud <thibaudm@chromium.org>
    Commit-Queue: Clemens Backes <clemensb@chromium.org>
    Cr-Commit-Position: refs/heads/master@{#70967}
    c6c86944
api.cc 438 KB