On 12/3/17 00:09, Dmitry Olshansky wrote:
On Saturday, 2 December 2017 at 23:44:39 UTC, Walter Bright wrote:
On 12/2/2017 4:38 AM, Iain Buclaw wrote:
But then you need to bloat your program with debug info in order to
understand what, why, and how things went wrong.
Most of the time (for me) that isn't necessary, because the debugger
still shows where it failed and that's enough.
Besides, you can always rerun the test case with a debug build.
Ehm, if it’s a simple reproducable tool.
Good luck debugging servers like that.
I have to agree with this. I make my living on server side software, and
we aren't allowed (by legal) to connect to the server to run debuggers.
The *only* thing I have is logging. If the program crashes with no
option to trap an exception or otherwise log the crash this could cost
me weeks-to-months of debugging time.
--
Adam Wilson
IRC: LightBender
import quiet.dlang.dev;
