| OLD | NEW |
|---|
| 1 ## 1.3.6 | 1 ## 1.4.0 |
| 2 | 2 |
| 3 * `new Trace.parse()` and related constructors will no longer throw an exception |
| 4 if they encounter an unparseable stack frame. Instead, they will generate an |
| 5 `UnparsedFrame`, which exposes no metadata but preserves the frame's original |
| 6 text. |
| 7 |
| 3 * Properly parse native-code V8 frames. | 8 * Properly parse native-code V8 frames. |
| 4 | 9 |
| 5 ## 1.3.5 | 10 ## 1.3.5 |
| 6 | 11 |
| 7 * Properly shorten library names for pathnames of folded frames on Windows. | 12 * Properly shorten library names for pathnames of folded frames on Windows. |
| 8 | 13 |
| 9 ## 1.3.4 | 14 ## 1.3.4 |
| 10 | 15 |
| 11 * No longer say that stack chains aren't supported on dart2js now that | 16 * No longer say that stack chains aren't supported on dart2js now that |
| 12 [sdk#15171][] is fixed. Note that this fix only applies to Dart 1.12. | 17 [sdk#15171][] is fixed. Note that this fix only applies to Dart 1.12. |
| (...skipping 110 matching lines...) Expand 10 before | Expand all | Expand 10 after Loading... |
| 123 | 128 |
| 124 * If an error is thrown in `Chain.capture`'s `onError` handler, that error is | 129 * If an error is thrown in `Chain.capture`'s `onError` handler, that error is |
| 125 handled by the parent zone. This matches the behavior of `runZoned` in | 130 handled by the parent zone. This matches the behavior of `runZoned` in |
| 126 `dart:async`. | 131 `dart:async`. |
| 127 | 132 |
| 128 ## 0.9.3 | 133 ## 0.9.3 |
| 129 | 134 |
| 130 * Add a `Chain.foldFrames` method that parallels `Trace.foldFrames`. | 135 * Add a `Chain.foldFrames` method that parallels `Trace.foldFrames`. |
| 131 | 136 |
| 132 * Record anonymous method frames in IE10 as "<fn>". | 137 * Record anonymous method frames in IE10 as "<fn>". |
| OLD | NEW |
|---|
Chromium Code Reviews
Issue 1283113002:
Don't throw for unparseable frames. (Closed)
Base URL: git@github.com:dart-lang/stack_trace@master