title: Is invocation of exception.fillInStacktrace useful?
body: <p>I found an explicit invocation of <code>e.fillInStacktrace()</code> directly after creation of the exception <code>Exception e = new Exception()</code>.</p>
  
  <p>I think this is redundant, because the constructor of <code>Throwable</code> already invoke <code>fillInStacktrace()</code>.</p>
  
  <p>But maybe I overlooked something and this lines are useful:</p>
  
  <pre><code>Exception e = new Exception();
  e.fillInStackTrace();
  creationInfo = new CreationInfo(e.getStackTrace());
  </code></pre>
  
  <p>(<code>public CreationInfo(StackTraceElement[] aStackTrace){...}</code>)</p>
  
  <p>I think</p>
  
  <ol>
  <li><p>the additional invocation of <code>e.fillInStackTrace();</code> directly after creation an exception is redundant and will wast a lot of resource, because this method is expensive.</p></li>
  <li><p>It seams that this construct is only needed to obtain the current stacktrace, therefore:</p>
  
  <pre><code>creationInfo = Thread.currentThread().getStackTrace();
  </code></pre>
  
  <p>is the better way.</p></li>
  </ol>
  
  <p>Before filling an issue report I want to ask you if I have overlooked something?</p>