I sometimes encounter bugs that involve a recursion limit. It's often very hard to find the origin of the problem.
Would there be a way to copy the stack somewhere and abort the evaluation in order to know what is causing the error when a message such as the following is emitted (this is just an example)?
t = {t}
$RecursionLimit::reclim2: Recursion depth of 1024 exceeded during evaluation of {t}
In practice I have a complex program with a user interface and I can't know what's triggering the recursion. Also in Wolfram Workbench, the message breakpoint doesn't stop on such message.