Chrome error rethrow - now points to the location of the throw instead of the location of the original error. How to fix?

Question

JavaScript

The library uses the following wrapper to execute custom code:

try {
    exec(callback)
} catch (e) {
    setTimeout(function(){throw e})
}

For a number of reasons, the code itself cannot be isolated in setTimeout (an explicit execution order is required). Error throw is also necessary for debugging custom code.
Previously, this method duplicated the original error and showed its place. Right now it points to setTimeout(function(){throw e}), which doesn't really help debugging. There are no traces, of course. Is it possible to somehow fix it?

Answer 1

What is setTimeout for here?