Whenever a unit test fails due to a `StackOverflowException` the unit test process immediately exits - the only way to find out what happened (that I am aware of) is to debug a crash dump of the unit test process obtained by following the steps found here

* [Collecting User-Mode Dumps](http://msdn.microsoft.com/en-us/library/bb787181%28VS.85%29.aspx)

What is the easiest way of getting the name of the unit test that was running at the time that the `StackOverflowException` was thrown? Even when debugging the unit test I'm struggling to find the name of the current unit test as its at the bottom of the stack and Visual Studio wont' shown the entire stack in the debugging window because its too large.

Is there some way to find out which unit test failed without collecting and debugging crash dumps?
['https://Stackoverflow.com/questions/15337469', 'https://Stackoverflow.com', 'https://Stackoverflow.com/users/113141/']
Use [Eclipse](http://www.eclipse.org/). Cloudera has a great screencast [here](http://blog.cloudera.com/blog/2009/04/configuring-eclipse-for-hadoop-development-a-screencast/) for configuring eclipse for hadoop development.
Also debugging a hadoop job locally is pretty cool using eclipse (though not trivial). To know more on that, see [here](http://amnigos.com/post/44631353593/how-to-guide-hadoop-mapreduce-debugging-in-lo).
Yes, It's possible to run the MapReduce jobs in Eclipse. There is a lot of difference running MapReduce programs on a cluster and in Eclipse.
Bellow are the few points worth noting:

* In Eclipse, it runs in a special mode called: LocalJobRunner mode i.e. all Hadoop daemons are run in single JVM.
* In Eclipse, All paths refer to local file paths, and not to HDFS path.