Jump to content
  • Advertisement
Sign in to follow this  
coderWalker

Eclipse Debugger

This topic is 2708 days old which is more than the 365 day threshold we allow for new replies. Please post a new topic.

If you intended to correct an error in the post then please contact us.

Recommended Posts

My game keeps crashing and I want to close in on the problem.

However when I use the debugger and click advance line I can go for about 200 lines and
I don't hit the problem. So I click "|> Continue execution" then it shows one line and it crashes.

I need to know how it got to that line. Is there a way to run the program in slow motion
or something? How should I go about locating this problem?

Share this post


Link to post
Share on other sites
Advertisement
When the program crashes, the debugger should break at the offending line. From there you can examine the call stack in order to find out which methods were called in order to get to that line.

Btw., I don't know if I understood you correctly, but usually when using a debugger, you don't just start the program, break at the first line, and then step through every single line. Since you know which line it crashes in, you set a break point just before the line and examine the values of your variables, the call stack, etc. to find the cause of the problem.

Share this post


Link to post
Share on other sites
Sign in to follow this  

  • Advertisement
×

Important Information

By using GameDev.net, you agree to our community Guidelines, Terms of Use, and Privacy Policy.

We are the game development community.

Whether you are an indie, hobbyist, AAA developer, or just trying to learn, GameDev.net is the place for you to learn, share, and connect with the games industry. Learn more About Us or sign up!

Sign me up!