Re:Developer tools can be magic but instead collect dust
by kaba0 on Sunday March 28, 2021 @07:32PM
(#26615904)
I’m sorry but that just means you have not have learnt how to use debug tools.
Re:Developer tools can be magic but instead collect dust
by heavenlyblue on Monday March 29, 2021 @08:48AM
(#26620741)
No, I know how to use them, except that in my cases I never need to look a the debugger because I rarely need to know the state of the program at a given time.
I need to know how the program ended up in that state. I can't reproduce this from a core dump or via a debugger.
Re:Developer tools can be magic but instead collect dust
by ynx on Monday March 29, 2021 @12:26PM
(#26624234)
> I can't reproduce this from a core dump or via a debugger.
Because you don’t know how to debug. Time travel debugging does exactly this.
Re:Developer tools can be magic but instead collect dust
by govtman on Monday March 29, 2021 @05:32PM
(#26628441)
You can... are you familiar with the concept of a call stack?
Re:Developer tools can be magic but instead collect dust
by dan-robertson on Sunday March 28, 2021 @06:17PM
(#26615224)
That’s definitely not what a debugger is. You can’t add prints to a coredump and the run->add prints->compile->loop sucks a lot, especially if the bug is hard or slow to trigger.
I think the main promise of an IDE is being integrated. But maybe it could just be done with libraries.
Re:Developer tools can be magic but instead collect dust
by heavenlyblue on Monday March 29, 2021 @08:48AM
(#26620751)
> You can’t add prints to a coredump and the run->add prints->compile->loop sucks a lot, especially if the bug is hard or slow to trigger.
Yeah, but the core dump doesn't give you an answer on how the program ended up in failure state, does it?
Re:Developer tools can be magic but instead collect dust
by higerordermap on Monday March 29, 2021 @11:24AM
(#26623127)
Use something other than DDD?
Re:Developer tools can be magic but instead collect dust
by dmz73 on Sunday March 28, 2021 @06:21PM
(#26615263)
Debugger might be a nice interface for prints in kernel.
It is also not usable with distributed systems where prints are also not all that useful and you need some kind of central logging.
But developing a desktop application without debugger is like writing code with a line editor. It can be done but it is not very productive (I can still remember editing BASIC programs one line at the time).
Re:Developer tools can be magic but instead collect dust
by heavenlyblue on Monday March 29, 2021 @08:49AM
(#26620759)
I meant "prints" as in "logging events into a file".
IDEs should be replaced with libraries that allow one to operate over the code (or make IDEs allow you to script their AST manipulators)
Writing tests is not connected to the two above.