Assert failure on 2.070.0 without stack trace

[Nordlöw via Digitalmars-d-learn]

On Thursday, 28 January 2016 at 18:13:59 UTC, Vladimir Panteleev 
wrote:
> You can use Digger to find the exact compiler change that 
> caused this assert to manifest, and Dustmite to find the 
> minimal program which behaves differently in two compiler 
> versions.

Thanks, I'm aware of these tools.

But it's easier to use the stacktrace...if I only get one. The 
function where the assert() is called is, in turn, called in 
hundreds of places.