This quote is amazing lol
[1] http://www.gamasutra.com/blogs/DaveBaggett/20131031/203788/M...
11–17 of 17 posts
This quote is amazing lol
[1] http://www.gamasutra.com/blogs/DaveBaggett/20131031/203788/M...
Maybe one could ask the authors if they could donate their debugging articles to a cc licensed repository so the articles themselves could be hosted instead of linking? That would be very nice I think.
For some reason i love reading these kind of stories, especially when you get the feel the writer is venting after a deep dive of the OS guts. A close equivalent is reading Derek Lowe's "things i won't work with" articles.
I absolutely loved the "Things I won't work with" articles, very enjoyable to read. And I even learned some things about chemistry in the process. I can only recommend everybody who is even slightly interested in chemistry to read them.
x = (Item*)malloc(sizeof(Item));
memset(x->name, 0, 12);
strcpy(x->name, name);
x->flag = flag;
So the bits after name are now significant in compares but expected to be zero because of memset. Well the optimizer would effectively remove the memset in release builds due to the strcpy so the code worked most of the time in release but would occasionally break because the bytes after the null terminated name could be anything and would only come into play when name was the same for 2 items.Earlier quoted context omitted.
I absolutely loved the "Things I won't work with" articles, very enjoyable to read. And I even learned some things about chemistry in the process. I can only recommend everybody who is even slightly interested in chemistry to read them.
http://pipeline.corante.com/archives/things_i_wont_work_with...
http://blogs.sciencemag.org/pipeline/archives/category/thing...
http://nanxiao.me/en/an-experience-of-fixing-a-memory-corrup...
is really dumb. The moral is that you don't use global variables that are accessed by multiple threads (unless you're very careful). That's C programming 101.