Comments on: Debugging Memory Corruption in Game Development

By: baju korea

baju korea — Fri, 04 Dec 2009 10:53:46 +0000

nice post, When talking about game development as a whole, it is difficult to cover all the major symptoms of memory corruption. I think your article offers some great starting points for debugging.

By: Alexander Churanov

Alexander Churanov — Thu, 03 Dec 2009 16:19:12 +0000

Nobody mentions the valgrind. It’s more effective than some medieval approaches.

By: iphone application developers

iphone application developers — Thu, 15 Oct 2009 06:43:36 +0000

nice post, When talking about game development as a whole, it is difficult to cover all the major symptoms of memory corruption. nice programming tips..
thank you..

By: Baju Muslim

Baju Muslim — Mon, 12 Oct 2009 16:40:18 +0000

I often deal with debug web development, I often spend much time on it. but seeing this article how to debugging game development, makes me think that debug a web is far easier.

Nice article.

By: busana muslim

busana muslim — Wed, 05 Aug 2009 02:47:25 +0000

nice post, When talking about game development as a whole, it is difficult to cover all the major symptoms of memory corruption. I think your article offers some great starting points for debugging.

By: Shaw

Shaw — Mon, 05 Jan 2009 03:02:54 +0000

Woah, I gotta admit, I’m definitely more of the user than the programmer, but I tell you, sometimes I bit** about how much games cost, but then I see what really goes into making things come together…So I guess, to some extent, it is worth the few bucks I spend for hours of glitch free entertainment! Shaw

By: pixelame.net

pixelame.net — Sat, 11 Oct 2008 21:22:42 +0000

Memory Corruption en el desarrollo de videojuegos…

Este interesantísimo artículo de Mick West nos habla de la corrupción de la memoria durante la programación de videojuegos y qué se puede hacer si ocurre….

By: Busana Muslim

Busana Muslim — Wed, 08 Oct 2008 11:11:22 +0000

nice programming tips..
thank you..

By: Mick West

Mick West — Tue, 16 Sep 2008 15:38:34 +0000

Ah yes, I think I had planned to add caching and DMA bugs, and probably multi-threading – all of which can cause memory corruption in ways that are very very difficult to track down.

By: systematicgaming

systematicgaming — Tue, 16 Sep 2008 07:54:33 +0000

Not many people discuss such specific debugging issues. I agree everyone above, great article.

You’re missing a my favorite reason – caching issues. Most common in graphics bugs, and not visible by the debugger. Fun!

You also didn’t mention my one of my pet peeves with programmers who just claim that every “random” crash is due to someone else stomping on memory, instead of actually debugging the issue.