Hi everyone,
Once I was googling and came across one thing: Declarative Debugging for Java
What do you think about this software?
I don’t use debuggers, I’m perfect. 
<sub>[sub]*Sweeps NullPointerException under the rug*</sub>[/sub]Same. I just use system.out.print and try-catch. No need for that imho.
It’s going to be hard to really know what this software even does without some examples, so as of now I don’t think much about it.
However, it does remind me of attempts to prove a program’s “correctness” at compile-time. It’s a very difficult and slightly interesting problem.
Languages like Dafny and libraries like OSE CSE Components attempt to solve this problem, and they’re worth checking out if you’re into this sort of thing.
I too use Console output and some times (which is very, very rare. More rare than me not fancying a pizza at any given time a day) breakpoints.
Had to use the VS 2013 debugger occasionally for school, but I hated it.
Same. If something’s not working, I’ll first look through the code for some obvious problems (local variables instead of global variables), identify what’s not working, put a bunch of [icode]System.out.println(“Working”);[/icode]s in there, and see if that fixes the problem. If not, I resort to google or these forums.
Yea that’s what makes a programmer, problem-solving and logic.
And pizza. Don’t forget the pizza. :point:
I just click Compile-Run until I can’t see the bugs any more.
I often use print too, but in some specfic cases I use debuggers (like DDMS for Android).
Typically throw in prints if I know it will tell me what I need to know, or at least believe it’s a data issue.
Debugger for things were that’s inconvenient (e.g. library calls) or it’s a control flow problem that prints wouldn’t do well with.
Example necessity debugger was when I had to debug R-Tree construction and query in a dll (no stdout to print to, printing to file would be too expensive) called from a program I didn’t have the source to.
Thanks, gdb.
Actually, the IntelliJ debugger saved me hours of frustration at work today.
Debugging tools are a godsend sometimes, and I pray to whatever man created them. Other days, I lazily throw some print statements around. It really depends on the severity of the error to me, and how I’m feeling.
I normally use print statements in Java. The Eclipse debugger doesn’t feel nice for me to use so I avoid it, whereas I love it in Visual Studio. Eclipse console output is clear though and having a quick shortcut to create a print statement makes me want to use that. My projects haven’t really moved out the Java desktop environment, so I’m not sure what the implications are beyond that.
I’m not sure debuggers are that essential in Java where errors print out a nice comprehensive message and stacktrace.
In low-level languages where you can get hit by a segfault out of nowhere, there you need a debugger.
this :point:
Mostly “syser” + [Ctrl+Space] + [Enter] in Eclipse and adding the stuff I want to see
But I really like debugging with features like conditional breakpoints and such - used right it can help a lot
try/catch all the things!
I remember hearing about her somewhere. I believe it was actually in high school… most likely my AP CS class? It gave us all a good laugh!