December 15, 2005
Comments are Back

An unfortunate Debian bug broke lemonodor for part of yesterday and today. Sorry for the hassle, especially if you tried to post a painstakingly crafted refutation of why ASDF-INSTALLable library quality matters and were rewarded with the following:

  Got an error: Unsupported driver MT::ObjectDriver::DBM: 
  DB_File needs compatible versions of libdb & db.h
    you have db.h version 4.3.29 and libdb version 4.3.28

My gracious admin Andreas has fixed the problem, so please try again.

Posted by jjwiseman at December 15, 2005 11:11 AM

Actually, I was trying to write an eloquent passage about how shitty the new VS2005 64-bit compiler is.

But since then I found out it was even crappier than I thought.

void bigStack() { char tooBigFor64[1024*1024]; }
int main(int c, char **v) { bigStack(); return 0; }

You can compile this in 32-bit and 64-bit modes, but you can't run it in 64-bit mode or you get stack corruption. You can tell instantly when you attempt to debug into the function. It tells you... stack frame lost.

What's more awesome than expected 1M stack limitation issues? Not being able to change it. /F and /STACK are the options for modifying stack size defaults, but they seem to have no effect.

What's even more awesome? The limit appears to be a char buffer of 500k. 600k breaks the same as 1M.

32-bit/64-bit linux are just fine with this (and have default stack sizes of 2M-8M depending on kernel, i hear).

Anyway, the fun part is spending hours and hours trying to narrow down the issue not knowing what part of thousands of lines of code was causing it and being able to reproduce it with two lines of code..

This is why C++ is so superior to Lisp!

Posted by: sweet on December 15, 2005 03:31 PM
Post a comment

Email Address:


Unless you answer this question, your comment will be classified as spam and will not be posted.
(I'll give you a hint: the answer is “lisp”.)


Remember info?