From db94aa94eb3fccc9c53e0cccd11bdb7d8d17d8ef Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Ivan=20=C5=BDu=C5=BEak?= Date: Wed, 4 Jun 2014 17:22:55 +0200 Subject: [PATCH] Mention how to get the full stack trace for errors --- CONTRIBUTING.md | 5 ++++- 1 file changed, 4 insertions(+), 1 deletion(-) diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md index da8163abc..2d2fc34fc 100644 --- a/CONTRIBUTING.md +++ b/CONTRIBUTING.md @@ -15,7 +15,10 @@ propose changes to this document in a pull request. helpful. * Include the behavior you expected and other places you've seen that behavior such as Emacs, vi, Xcode, etc. -* Check the dev tools (`alt-cmd-i`) for errors and stack traces to include. +* Check the dev tools (`alt-cmd-i`) for errors to include. If the dev tools + are open _before_ the error is triggered, a full stack trace for the error + will be logged. If you can reproduce the error, use this approach to get the + full stack trace and include it in the issue. * On Mac, check Console.app for stack traces to include if reporting a crash. * Perform a cursory search to see if a similar issue has already been submitted.