Stack trace tool

Whenever you encounter an error in your application, you want to be able to quickly debug the problem. Initially, developers should look in the application logs for the stack trace, because often, the stack trace tells you the exact line or function call that caused a problem. In addition to telling you the exact line or function that caused a problem, a stack trace also tracks important metrics that monitor the health of your application.

For example, if the average number of stack traces found in your logs increases, you know a bug has likely occurred. Furthermore, a low level of stack trace exceptions indicates that your application is in good health. In short, stack traces and the type of errors they log can reveal various metrics related to your application as explained in the example. Often, your projects will use many third-party code packages or libraries. There is a rich ecosystem of packages maintained by the Open Source community.

In some cases, an error occurs when you send incorrect input to one of the third-party libraries you use. As you might expect, your program will print a stack trace of the function calls leading up to the problem.

In some cases, like when too many function calls happen within a third-party package, you may not even see any references to your code. You can still try to debug your code by looking at where a particular package was used. Luckily, you can solve third-party stack trace problems by catching exceptions. A call to a third-party library may cause an exception, which will cause your program to print a stack trace containing function calls coming from within the third-party library.

However, you can catch the exception in your code with the use of a try-catch statement , which is native to many programming languages such as Java or Node.

If you use a try-catch statement, the stack trace will start from the point where you included the try-catch logic. On top of that, when your program throws a Throwable instance , you can call the getStackTrace function on the instance to access the stack trace.

You can then decide to print the stack trace to your terminal so you can collect the information for log analysis. A logging solution provides you with an easy-to-use interface and better filtering capabilities. A log management solution helps aggregate logs, index them, and make them searchable, all from a single interface. You can run advanced queries to find specific logs or stack trace information. To receive further information, fill out the request form below.

OSTI staff will begin to process an order for scientific and technical software once the signed site license agreement is received. You may also reach us by email at:. Title: Stack Trace Ahalysis Tool. Abstract STAT is a light weight debugging tool that gathers and merges stack traces from all of the processes in a parallel application. Authors: Lee, Gregory L. Lee, Gregory L. Stack Trace Ahalysis Tool. Computer software. Copy to clipboard. Version January 12, Man pages are also available man stat-gui.

The attach dialog allows you to select the application to attach to. By default, the attach dialog searches the localhost for the job launcher process, but you may specify an alternative hostname in the Search Remote Host text entry field. Thus, you may attach STAT to a batch job from a login node. On TOSS systems, the appropriate host is usually the lowest numbered node in your allocation. In general, to find the appropriate node, you may be able to run:.

When you left click on a node in the graph, you will get a pop-up window that lists the function name and the full set of tasks that took that call path. Right clicking on a node provides a pop-up menu with the same options.

The pop-up window has several buttons that allow you to manipulate the graph, allowing you to focus on areas of interest. Each button is defined as follows:. The main window also has several tree manipulation options note all of these operate on the current, visible state of the tree :.