3 ms·
They are useful sure, and I print a stacktrace on any type of error/exception, but often breaking into the debugger is even more useful and faster as you can se
by TinkersW 2y ago
They are useful sure, and I print a stacktrace on any type of error/exception, but often breaking into the debugger is even more useful and faster as you can see local variables, program state, and what other threads happen to be doing.
- piva00 2y agoHard to break into the debugger for a production application running on hundreds of servers.
- TinkersW 2y agoPerhaps, but remote debugging is a thing, though triggering an auto break into debugger would be more complex.
- piva00 2y agoRemote debugging is a thing but not very practical when you have hundreds of instances of your application running across dozens/hundreds of servers. For smaller scale apps it's a godsend but I haven't worked in that environment in more than a decade so remote debugging is essentially useless in my work.
- Cthulhu_ 2y agoOne can argue whether stack traces should be enabled for production (at least on all servers) given they're relatively expensive to create. Which isn't a problem if they're exceptional, but in a lot of cases they aren't.
- xmcqdpt2 2y agoThey aren’t equally expensive everywhere. They are cheap on the JVM.