|
| cat_plus_plus wrote:
| When I was young, we programmed in the debugger all the time! And
| we liked it!
| https://everything2.com/title/Writing+.com+files+with+DOS+de...
| tester756 wrote:
| This is debugger driven development
|
| In programming environments with very powerful debuggers like
| .NET this is relatively common since it allows you to do a lot of
| stuff at fly.
|
| Change values, evaluate expressions, change function's code, jump
| ahead and behind, etc, etc.
|
| Once you try this you'll never want to go back to print-debugging
| (except for specific cases)
| tcoff91 wrote:
| sometimes though when debugging multithreaded code,
| tracing/logging is easier to figure out what's going on vs
| pausing on breakpoints.
| tester756 wrote:
| >(except for specific cases)
|
| Exactly, that's what I meant
| tcoff91 wrote:
| I just remembered the Tracepoint feature though (it's been
| a while since I was working in C++ with visual studio).
| Even when you can't pause execution to debug it's still
| better to add your tracing in the debugger rather than
| having to make code changes.
|
| I was always doing stuff on windows/macOS/iOS/Android
| client libraries so I was always jealous of linux systems
| programmers who get to leverage Mozilla's rr tool. That's
| the coolest debugging tool I've ever seen.
| Conscat wrote:
| Sadly rr cannot work on software that makes any kind of
| call to GPUs, so its usefulness is pretty limited on a
| lot of larger software. But when it's usable, imo it's
| amazing.
___________________________________________________________________
(page generated 2023-09-28 23:00 UTC) |