Nathan,

Try this patch:

diff --git a/dart/sdk/lib/_internal/lib/js_helper.dart b/dart/sdk/lib/_internal/lib/js_helper.dart
index 2e350b7..7cba4fd 100644

--- a/dart/sdk/lib/_internal/lib/js_helper.dart
+++ b/dart/sdk/lib/_internal/lib/js_helper.dart
@@ -1419,7 +1419,12 @­@ unwrapException(ex) {
  * Called by generated code to fetch the stack trace from an
  * exception. Should never return null.
  */
-StackTrace getTraceFromException(exception) => new _StackTrace(exception);
+StackTrace getTraceFromException(exception) {

• _StackTrace trace = JS('_StackTrace|Null', r'#.$cachedTrace', exception);
• if (trace != null) return trace;
• trace = new _StackTrace(exception);
• return JS('_StackTrace', r'#.$cachedTrace = #', exception, trace);
  +}
   
   class _StackTrace implements StackTrace {
     var _exception;

I'm at home without VPN right now, but I'll try to get this submitted tomorrow.

Cheers,
Peter

Set owner to @peter-ahe-google.
Added Started label.

That works great, thanks!

https://codereview.chromium.org/78343002

I'd like to cast a vote in support of getting this CL in!

What's the priority?

I'd certainly like to see this patch land, but it's not blocking me personally since I don't do any debugging in the browser.

The CL https://codereview.chromium.org/78343002 has met surprising resistance from the VM team. So I'm stuck.

Peter, you mention on the code review that the language team would discuss to come to a decision. Do we know if they did?

The objection to CL 78343002 seems to be that this isn't a guarantee we want to offer, but this guarantee is crucial to making stack chain tracking work. I contend that breaking stack chains is an unacceptable usability regression, so we should commit to guaranteeing identity equality of stack traces.

I agree with Nathan.

Emily: I not sure those meetings exist anymore.

@peter, yes, but I'm curious if it was actually discussed back when they did.

I don't think it was ever discussed. I don't recall seeing anything about it in Bob's minutes.

Marked this as being blocked by #18394.

I hope that we will agree on guaranteeing that the stacktraces are identical (I just pinged issue #18394 to follow up on that).

Regardless of that discussion, I'd like to push forward the change Peter proposed earlier. Doing so will make it easier for people to debug async stack traces, and it will make the dart2js consistent with the current VM behavior.

If and when we decide that we don't want those guarantees and the VM needs to change the behavior in the future, we can revisit this at that point.

cc @peter-ahe-google.
Set owner to @sigmundch.

just sent out https://codereview.chromium.org/1152023004/

Looks like the new language in the spec actually now requires that rethrow gives you the same stack trace object (see discussion in issue #18394), so we should be good to go.

Forgot to close this - this was fixed in 1763aa3