Jump to content
  • Advertisement
Sign in to follow this  
  • entries
  • comments
  • views


Sign in to follow this  
Evil Steve



I spent a total of 6 hours over Monday and today tracking down a bug, that turned out to be completely unrelated to the stuff CodeWarrior was sending to the debug output.

The reason? CodeWarrior ditches debug log statements to stop it slowing down. So if you write out 10 lines, one after the other, you'll only get 8 or so printed out. Not just the first 8, a random 8. Sometimes parts of one line spliced with parts of another line.

Now, on the DS, where the debug output is just about the only way to debug stuff (Debug builds got broken a couple of weeks ago due to some optimizations that CodeWarrior can't cope with), not having a working debug output is just fucking rediculous.

I'm so pissed off right now.
Sign in to follow this  


Recommended Comments

Sounds like loads of fun.

I recently spent almost three days tracking down a bug in a DS clone child (ie, no debugging, no code stepping, only debug out). Finally found it was a stack overflow caused by a sprintf statement!

Share this comment

Link to comment
Original post by rick_appleton
Finally found it was a stack overflow caused by a sprintf statement!
That's why we get crucified for using sprintf() here. snprintf() ftw.

Share this comment

Link to comment

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
  • Advertisement

Important Information

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

GameDev.net is your game development community. Create an account for your GameDev Portfolio and participate in the largest developer community in the games industry.

Sign me up!