You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Today if we call Debug::print_stack_trace, it prints a stack with very low-level data: bytecode, stack information and etc.
This however isn't typically what a Move developer wants.
The basic thing a developer want to see would be the similar kind of stacktrace in other languages: the file and line number of each function in the stack.
The text was updated successfully, but these errors were encountered:
Today if we call
Debug::print_stack_trace
, it prints a stack with very low-level data: bytecode, stack information and etc.This however isn't typically what a Move developer wants.
The basic thing a developer want to see would be the similar kind of stacktrace in other languages: the file and line number of each function in the stack.
The text was updated successfully, but these errors were encountered: