in reply to Warn stack trace lost its way?
You might find a couple of ideas in the thread at HOWTO: Finding errors "at (eval 469) line 3".