Comment 8 for bug 1964120

It appears the address of a stack variable has overwritten the return address for the offending function call. So we have no stack trace.

I wonder if there's a way to catch stack corruption without going so far as Valgrind...