If you are a Team BlackOut follower, I assume you have read DJ's instructions on giving us a log before. It is simple and logical, but the information we need is not necessarily always in the screenshots you send us via that method.
YOU MUST BE ROOTED IN ORDER TO GET A LOGCAT (with apps like Catlog, matlog, or by using ADB).
PLEASE NOTE, THIS DOES NOT WORK FOR KERNEL RELATED ISSUES! Getting the "last_kmsg" from /proc/ is the best method for random reboots and other kernel related problems.
1. Search for, and download, Matlog from the Play Store (or the Holo version floating around xda; I assume it works the same)
Play Store Listing
2. Long press on your homescreen, create the Matlog widget (1x1)
3. Click on the Matlog widget. This will prompt a dialog for you to change/confirm the name for the log's .txt file (if you so please)
4. Repeat the action (such as opening an app) that caused you to get a force close.
5. As soon as you get the "XXX has force closed/stopped working", go back to your homescreen (or whichever screen you placed the widget on) and click on the widget again. NOTE: This will open your recorded log within the Matlog app. Unless you know how to debug, you don't need to worry about that...you can just close it.
6. After exiting the log that you just recorded, open up the file explorer of your choice. Scroll down until you see the "catlog" folder. Inside of that will be "Saved Logs", which is where you will find the .txt file containing the recorded logcat.
7. Then send that puppy on over to your developer of choice.
AND THAT'S IT! (Although, I must say...Please send them in a PM unless the devs specify otherwise. Logs quickly clutter threads IMO)