On Thu, 3 Apr 2008, Sven Schreiber wrote:
I haven't been able to find a stripped-down testcase so far;
however, I have some more information on my case -- sorry for
the longish explanation, but that's all I can come up with. I
could prepare a non-stripped-down testcase tomorrow if that's
useful.
Yes, a non-stripped-down testcase would still be helpful.
BTW, during debugging (using a bunch of 'funcerr'
statements), I
stumbled over other quirks:
1) At some point I got an error saying "IF depth exceeded" or
something like that. Now I don't nest that many IF blocks, so I
guess this happened because I repeatedly interrupted functions
in the middle of IF blocks by using 'funcerr'. But that suggests
that some "stacks" (or whatever they're called) are not properly
cleaned up when a function exits with an error...
Yes, I suppose that must be the case.
2) For weeks now I have often got errors about allegedly
"missing values found" which were all bogus. These errors are
not robust...
This sort of flakiness sounds like a memory-management issue.
I can run your test case through valgrind.
Thanks for reading until the end!
And thanks for writing to the end.
Allin.