• Post Reply Bookmark Topic Watch Topic
  • New Topic
programming forums Java Mobile Certification Databases Caching Books Engineering Micro Controllers OS Languages Paradigms IDEs Build Tools Frameworks Application Servers Open Source This Site Careers Other all forums
this forum made possible by our volunteer staff, including ...
  • Campbell Ritchie
  • Liutauras Vilda
  • Bear Bibeault
  • Paul Clapham
  • Jeanne Boyarsky
  • Devaka Cooray
  • Junilu Lacar
  • Tim Cooke
Saloon Keepers:
  • Tim Moores
  • Ron McLeod
  • Tim Holloway
  • Claude Moore
  • Stephan van Hulst
  • Winston Gutkowski
  • Carey Brown
  • Frits Walraven

Eclipse debugging issue.  RSS feed

Ranch Hand
Posts: 98
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
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?

That's the best I can give you.
Posts: 563
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Parts of your post are confusing:

"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.

Good luck.
Everybody! Do the Funky Monkey! Like this tiny ad!
Become a Java guru with IntelliJ IDEA
  • Post Reply Bookmark Topic Watch Topic
  • New Topic
Boost this thread!