🎉 Celebrating 25 Years of GameDev.net! 🎉

Not many can claim 25 years on the Internet! Join us in celebrating this milestone. Learn more about our history, and thank you for being a part of our community!

Untitled

posted in DruinkJournal
Published September 20, 2006
Advertisement
FUCKING CODEWARRIOR.

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.
Previous Entry Untitled
Next Entry Holidays!
0 likes 4 comments

Comments

Programmer16
Codewarrior ftl.
September 20, 2006 04:00 PM
rick_appleton
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!
September 20, 2006 04:21 PM
Evil Steve
Quote: 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.
September 21, 2006 03:34 AM
rick_appleton
snprintf isn't the end all, be all. Changing the sprintf to snprintf had no effect on the bug!
September 21, 2006 10:52 AM
You must log in to join the conversation.
Don't have a GameDev.net account? Sign up!
Advertisement
Advertisement