--- Comment #16 from 2012-02-05 17:43:00 PST ---
(In reply to comment #14)

> In other words, it's always behaved erratically, and is not a regression.

I have just done a little binary search, and I've found that up to DMD 2.052,
DMD always shows "stack overflow", reliably, every time. And starting from DMD
2.053 it never shows "stack overflow". This test is done on the same machine,
so I think it's a problem inside the DMD zip and not outside it, like in the
operating system or its libs. So I think this is a regression, to be searched
inside the changed of 2.053.

> Nor do I think it is a serious problem, because it isn't caught by C or C++
> runtimes, nor for D on non-Windows platforms. It's just a nicety that druntime
> tries at all to catch this.

It's not a serious problem, but the missing stack overflow error has confused
me in the beginning. I have seen two other persons confused by the crash. One
of them was in D.learn:

A "stack overflow" message is a simple thing, but most programmers know what a
stack overflow is, and this avoids confusion. Knowing what's the cause of the
crash is useful if you don't run a debugger. If you know it's a stack overflow,
you start searching for bad behaving recursive functions in your program.

So while this is not a serious problem, DMD used to give this valuable
information to me until some time ago, and I'd like to have it back.

Configure issuemail:
------- You are receiving this mail because: -------

Reply via email to