Popular @
Forum Controls
Spotlight Features
The Rich Engineering Heritage Behind Dependency Injection
Andrew McVeigh takes us on a tour of the rich heritage behind dependency injection, what it represents, and tells us why its here to stay.
NetBeans 6: Matisse Updates
NetBeans 6 delivers great updates to the Matisse GUI builder. Spend a few minutes with Roman Strobl and get an expert briefing on what's new and what has changed. (sponsored)
Introduction to Groovy Part 3
In this, the third and final installation of Andres' Introduction to Groovy series, you learn about how Groovy handles variable numbers of arguments, named parameters, currying, and more about Groovy operators. Including, some new operators.
Easier Custom Components with Swing Fuse
Swing Fuse (actually just Fuse), is a framework designed to make it easier to create your own custom desktop components. In this article, Daniel Spiewak shows you how to get started and provides sample source code you can download.
Benchmark Analysis: Guice vs Spring
Willam Louth shows how he uses JXInsight Probes to investigate probable performance issues with code bases that he is not familiar with. He also highlights possible pitfalls in creating a benchmark, as well as in the analysis of results.
IntelliJ IDEA: Analyze external stack traces
At 1:33 PM on May 31, 2006, Alexandra Rusina wrote:
Fresh Jobs for Developers Post a job opportunity
Now imagine that you can simply copy an exception to your IDE and then navigate to source from the console. How much time will it save?
To save your time and make bug fixing a little less boring, IntelliJ IDEA provides you with the Stack Trace Analyzer. It works exactly as described above. Just click Analyze Stacktrace under the Analyze menu, and copy your stack trace in the dialog box. If your bug tracker or mail client corrupts stack traces (cut or wrap lines, etc.) then simply click Normalize.
IntelliJ IDEA can unscramble the stack trace. By default, it supports only Zelix KlassMaster, but others can be added by plugins (like ProGuard plugin). You only need to select your unscramble tool and specify the location of log file.
Click OK, and voila - you get the stack trace in the console and the navigation to source is available.
Got interested? Find more tips and tricks at IntelliJ IDEA blog.
3 replies so far (
Post your own)
Re: IntelliJ IDEA: Analyze external stack traces
Indeed, this is a nice feature. Unfortunately, IDEA 5.1.1 does not hyperlink my own classes obfuscated with ProGuard (see IDEADEV-4976). Maybe this can be fixed in 5.1.2?Mike
Re: IntelliJ IDEA: Analyze external stack traces
In fact, ProGuard is the third-party plugin. But anyway, JetBrains fixed this problem. The fix will be available in IntelliJ IDEA 6.0. You can already try it in the recent EAP version.Re: IntelliJ IDEA: Analyze external stack traces
Indeed a better feature.