dart-lang/tools monorepo.@pragma('vm:awaiter-link') to make package work better with Dart VM's builtin awaiter stack unwinding. No other changes.zoneValues to Chain.capture to be able to use custom zone values with the runZoned internal calls.repository field.test/chain/vm_test.dart, which incorrectly handles asynchronous suspension gap markers at the end of stack traces.Trace.parse and Chain.parse.>=2.12.0-0 <3.0.0 based on beta release guidelines.2.10.0 stable and dev SDKs.Trace.parse and Chain.parse. (Also fixed separately in 1.10.0-nullsafety.6)data: URIs that the Dart VM has used since 2.2.0.Chain.capture from Function(dynamic, Chain) to Function(Object, Chain). Existing functions which take dynamic are still fine, but new uses can have a safer type.<3.0.0.errorZone parameter to Chain.capture() that makes it avoid creating an error zone.Chain.forTrace() now returns a full stack chain for all StackTraces within Chain.capture(), even those that haven't been processed by dart:async yet.
Chain.forTrace() now uses the Dart VM's stack chain information when called synchronously within Chain.capture(). This matches the existing behavior outside Chain.capture().
Chain.forTrace() now trims the VM‘s stack chains for the innermost stack trace within Chain.capture() (unless it’s called synchronously, as above). This avoids duplicated frames and makes the format of the innermost traces consistent with the other traces in the chain.
Use official generic function syntax.
Updated minimum SDK to 1.23.0.
Trace.original field to provide access to the original StackTraces from which the Trace was created, and a matching constructor parameter to new Trace().onError callbacks for Chain.capture() in the parent zone.Trace.foldFrames() and Chain.foldFrames() now remove the outermost folded frame. This matches the behavior of .terse with core frames.
Fix bug parsing a friendly frame with spaces in the member name.
Fix bug parsing a friendly frame where the location is a data url.
Trace.parse(), Chain.parse(), treat the VM's new causal asynchronous stack traces as chains. Outside of a Chain.capture() block, new Chain.current() will return a stack chain constructed from the asynchronous stack traces.Add a Chain.disable() function that disables stack-chain tracking.
Fix a bug where Chain.capture(..., when: false) would throw if an error was emitted without a stack trace.
Chain.terse and Trace.terse.new Frame.caller() returned the wrong depth of frame on Dartium.new Trace.current() and new Chain.current() now skip an extra frame when run in a JS context. This makes their return values match the VM context.Chain.capture() generic. Its signature is now T Chain.capture<T>(T callback(), ...).StackTrace.current in Dart SDK 1.14 to get the current stack trace.Add a when parameter to Chain.capture(). This allows capturing to be easily enabled and disabled based on whether the application is running in debug/development mode or not.
Deprecate the ChainHandler typedef. This didn't provide any value over directly annotating the function argument, and it made the documentation less clear.
Chain.foldFrames() and Chain.terse when one of the chain's traces has no frames.new Chain.parse() now parses all the stack trace formats supported by new Trace.parse(). Formats other than that emitted by Chain.toString() will produce single-element chains.
new Trace.parse() now parses the output of Chain.toString(). It produces the same result as Chain.parse().toTrace().
data: URIs in stack traces.UnparsedFrame.toString().new Trace.parse() and related constructors will no longer throw an exception if they encounter an unparseable stack frame. Instead, they will generate an UnparsedFrame, which exposes no metadata but preserves the frame's original text.
Properly parse native-code V8 frames.
When a null stack trace is passed to a completer or stream controller in nested Chain.capture() blocks, substitute the inner block‘s chain rather than the outer block’s.
Add support for empty chains and chains of empty traces to Chain.parse().
Don't crash when parsing stack traces from Dart VM stack overflows.
Trace.terse on empty stack traces.new Trace.parseJSCore and new Frame.parseJSCore.LazyTrace.Chain.parse.Don't print the first folded frame of terse stack traces. This frame is always just an internal isolate message handler anyway. This improves the readability of stack traces, especially in stack chains.
Remove the line numbers and specific files in all terse folded frames, not just those from core libraries.
Make padding consistent across all stack traces for Chain.toString().
Add terse to LazyTrace.foldFrames().
Further improve stack chains when using the VM's async/await implementation.
terse argument to Trace.foldFrames() and Chain.foldFrames(). This allows them to inherit the behavior of Trace.terse and Chain.terse without having to duplicate the logic.Support VM frames without line or column numbers, which async/await programs occasionally generate.
Replace <<anonymous closure>_async_body> in VM frames' members with the terser <async>.
Unify the parsing of Safari and Firefox stack traces. This fixes an error in Firefox trace parsing.
Deprecate Trace.parseSafari6_0, Trace.parseSafari6_1, Frame.parseSafari6_0, and Frame.parseSafari6_1.
Add Frame.parseSafari.
Zone.errorCallback to attach stack chains to all errors without the need for Chain.track, which is now deprecated.Update the dependency on path.
Improve the formatting of library URIs in stack traces.
Chain.capture's onError handler, that error is handled by the parent zone. This matches the behavior of runZoned in dart:async.Add a Chain.foldFrames method that parallels Trace.foldFrames.
Record anonymous method frames in IE10 as “”.