stack_trace icon indicating copy to clipboard operation
stack_trace copied to clipboard

A package for manipulating stack traces and printing them readably.

Results 23 stack_trace issues
Sort by recently updated
recently updated
newest added

I try to get my StackTraces logged. It's working fine if I call: `print(Chain.current().terse);` StackTrace ```bash flutter: package:stacktrace_test/main.dart 36:35 HomePage.build. package:flutter/src/material/ink_well.dart 1183:21 _InkResponseState.handleTap package:flutter/src/gestures/recognizer.dart 275:24 GestureRecognizer.invokeCallback package:flutter/src/gestures/tap.dart 652:11 TapGestureRecognizer.handleTapUp package:flutter/src/gestures/tap.dart...

I currently get these here on a regular basis in Sentry: ``` StateError: Bad state: Future already completed File "future_impl.dart", line 18, in _Completer.completeError File "zone.dart", line 1666, in _RootZone.runBinary...

Very simple example: ``` void main() async { try { await g(); } catch (e) { print('catch e=$e'); } } Future g() { throw Exception('fake error'); } ``` As expected,...

for a long time, I had a problem with my flutter_command package, when the Command had caught an exception the stacktrace was always truncated. I created a simplified version of...

Hi, I wonder if it costs a lot of performance to call `Trace.current()` on a regular basis or should this be avoided and only done when absolutely needed? Cheers Thomas

Calling `Trace.current()` in debug works perfectly. However, calling `Trace.current()` in release mode yields a different stack which is definitely wrong (this code path is impossible). *Most*, if not all stack...

When building a web application using Flutter and WebAssembly, we will often have stack frames in callstacks that don't have the typical javascript format of somefile.js:123:45, but instead have an...

The VM started giving us different, significantly truncated `StackTrace` instances when running in the zone for `Chain.capture`. `Frame.caller()` relies on parsing `StackTrace.current` which no longer contains the caller we were...

The issue mentioned was to change the Trace format from `src\main.dart 27:15 main` to `src\main.dart:27:15 main` so that by clicking `(CTRL+click)` and it would open the file at that exact...

Currently, an example stack line looks like this: `src\main.dart 27:15 main` This looks really nice, however I would like an option for it to look like this: `src\main.dart:27:15 main` Note...