Repository navigation
Consider using package:stacktrace in flutter in --debug mode #3810
Description
@devoncarew says this can give us nicer stacktraces. Here is an example from the flutter_tools:
https://github.com/flutter/flutter/blob/master/packages/flutter_tools/lib/executable.dart#L80
Presumably we'd only need/want this in --debug mode?
Activity
Hixie commentedon May 10, 2016
I'm actually not really convinced they're better. They don't show the full filenames, for example, which messes with IDEs. I'm working on stuff on my test branch that will trim down the stack traces to be just the interesting frames, but that depends on them being in the format that StackTrace emits. If people want them to be prettier in other ways I'm happy to add support for that to the foundation library.
devoncarew commentedon May 10, 2016
Yeah, I think the nice part that the stack_trace package provides is a view across several async calls. We can do that ourselves; I think most of the work for that for stack_trace is done here: https://github.com/dart-lang/stack_trace/blob/master/lib/src/stack_zone_specification.dart.
Hixie commentedon May 10, 2016
Do you have an example (in Flutter specifically) where the cross-async-call stack_trace logic actually works and gives something useful?
devoncarew commentedon May 10, 2016
No, I haven't tried using it in flutter. I've found it useful - in dart:io apps - with code that uses
asyncor Futures. Exceptions (like this one: #3825) are easier to debug then if you only have the top set of frames.Hixie commentedon May 13, 2016
I'm going to close this in favour of the older #130 which is the more general issue on the same topic.
github-actions commentedon Sep 6, 2021
This thread has been automatically locked since there has not been any recent activity after it was closed. If you are still experiencing a similar issue, please open a new bug, including the output of
flutter doctor -vand a minimal reproduction of the issue.