Let's log a stack trace so that we can see where the damn error is, instead
of having an error triggered right after this one that happens to print a stack trace look like the matching stack trace for the original error. git-svn-id: svn+ssh://src.earth.threerings.net/narya/trunk@3679 542714f4-19e9-0310-aa3c-eee0fc999fb1
This commit is contained in:
@@ -273,6 +273,7 @@ public class SceneRegistry
|
||||
{
|
||||
Log.info("Failed to resolve scene [sceneId=" + sceneId +
|
||||
", cause=" + cause + "].");
|
||||
Log.logStackTrace(cause);
|
||||
|
||||
// alas things didn't work out, notify our penders
|
||||
ArrayList penders = (ArrayList)_penders.remove(sceneId);
|
||||
|
||||
Reference in New Issue
Block a user