3 ms·
Even just knowing the variables in the Stack frame is useful also. The error pages for Django and pyramid have this. Also, at a previous job someone created a t
by zitterbewegung 9y ago
Even just knowing the variables in the Stack frame is useful also. The error pages for Django and pyramid have this. Also, at a previous job someone created a toolbar that had all of the relevant server variables in your session.
- majewsky 9y agoAt a previous job, I built a server-side debugging tool which would record the requests that you made. For each request, you could see the HTTP request, the HTTP response, and events like SQL statements and log messages. (Sort of like Sentry.) There was also a button that re-ran the same request under a profiler. Sadly the tool was never merged into mainline, so the feature branch has probaly rotten away by now.
- vog 9y agoShlightly off-topic: Maybe it's just me, but this is exactly why I'm not a fan of feature branches. I do like to have local branches which sometimes serve as feature branches. But those are short-lived, so these either make it into mainline within a few days, or are deliberately marked as dead ends. (Or developed into a separate project, but this is very seldom and even then quickly moved into a new repository.)
- Ono-Sendai 9y agoA decent debugger will show all the local variables and their values.
- Mic92 9y agoMany variables are marked as optimized in debuggers - never in Inspector. This even happen sometimes to me, when compiler optimizations are disabled.