BETAmodules.com is in beta — open to partnerships & joint ventures.Build with us
modules.com
⌘K

power_trace

v0.3.0RubyGems· Ruby

Backtrace (Stack traces) are essential information for debugging our applications. However, they only tell us what the program did, but don't tell us what it had (the arguments, local variables...etc.). So it's very often that we'd need to visit each call site, rerun the program, and try to print out the variables. To me, It's like the Google map's navigation only tells us the name of the roads, but not showing us the map along with them. So I hope to solve this problem by adding some additional runtime info to the backtrace, and save us the work to manually look them up.

The verdict
Abandoned. Last published 5 years ago. No recent activity — look for a maintained alternative.
No recent activity — look for a maintained alternative.
Live from the RubyGems registry · derived rules, not AI
How it scores
MaintenanceAbandoned
PopularityNiche
SecurityClean
LicensePermissive
DepsZero deps
Maintenance
Last published 5 years ago.
Popularity
13 downloads / week
Security
No known advisories for this version (OSV).
License
MIT
Dependencies
No runtime dependencies
Recent releases
  • 0.3.05 years ago
  • 0.2.25 years ago
  • 0.2.15 years ago
  • 0.2.05 years ago
  • 0.1.05 years ago
power_trace — Backtrace (Stack traces) are essential information for debugging our applications. However, they only tell us what the program did, but don't tell us what it had (the arguments, local variables...etc.). So it's very often that we'd need to visit each call site, rerun the program, and try to print out the variables. To me, It's like the Google map's navigation only tells us the name of the roads, but not showing us the map along with them. So I hope to solve this problem by adding some additional runtime info to the backtrace, and save us the work to manually look them up. (Ruby / RubyGems) · Modules