News for hackers. Stuff that matters.

A comment on The unreasonable effectiveness of print debugging. Parent comment

Re:The unreasonable effectiveness of print debugging by zmmmmm on Saturday April 24, 2021 @05:39PM (#26928422)
The java case is actually pretty universal ... you run the JVM with debugging enabled (fixed string of flags) and then tell your IDE to attach to the JVM on the port you gave it. You don't need compileable source, can be on a remote server, different OS etc - if you have just the source for the bit you want to debug you can set a breakpoint in it and it'll stop there.

Being able to debug third party code in remote / hostile environments (even when its mixed with proprietary vendor code) is one of the things I like about Java.

[ Parent | on HN ]
Re:The unreasonable effectiveness of print debugging by foobarian on Saturday April 24, 2021 @10:42PM (#26929941)
The Java case is arguably the least difficult out there thanks to reasons you outline. But still, the other day I had to debug a Gradle plugin written in Java. It's possible! But it took an hour or so of effort to figure out which options to use and which program to give them to.
[ Parent | on HN ]