Categories: None [Edit]

power_trace

https://rubygems.org/gems/power_trace
https://github.com/st0012/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.

Total

Ranking: 85,807 of 190,317
Downloads: 10,453

Daily

Ranking: 98,986 of 190,280
Downloads: 1

Depended by

RankDownloadsName

Depends on

RankDownloadsName
71,293,977,679activesupport
44717,906,260rails
72583,359,451pry
265183,536,711binding_of_caller

Owners

#GravatarHandle
1iconst0012