This week's book giveaway is in the OCAJP 8 forum. We're giving away four copies of OCA Java SE 8 Programmer I Study Guide and have Edward Finegan & Robert Liguori on-line! See this thread for details.
Hey guys, I have this huge program that I'm working on, but I haven't built it. So I figured the best way to understand how it works is by running the debugger and stepping into everything as it happens. Wouldn't that be a good idea?
The program itself works fine. When I run the debugger (and set a random breakpoint), it will bring up a ton of issues before it even starts running it seems like. It won't even get anywhere.
I understand without providing much source code, you can't identify the problem. Can you tell me this much though:
1) Would debugging be a good way of delving into a program to understand how it works step-by-step?
2) Why is it receiving this issue now, but when I run the program normally, no issues come up?
3) Is there a way to ignore this issue?
4) Does it have to deal with the actual program itself?
"I haven't built it," "The program itself runs fine," and "A ton of issues . . . it won't even get anywhere," just don't go together.
Writing a huge program and then trying to figure out how it works is not a good approach, no matter how good the tools are. Writing a little, testing each component as you go, is a better approach. Now that you have this huge mass of code and aren't sure how it works, I suggest breaking it into smaller parts, restricting what is allowed to run, and test it a "chunk" at a time.
Always learning Java, currently using Eclipse on Fedora.
Linux user#: 501795