stack trace

(redirected from Stack traces)

stack trace

In program debugging, a stack trace is a report of the computer's internal processing operations. It generally identifies the last routine called in the program before it crashed. See stack and stack pointer.
References in periodicals archive ?
Beautiful reports: Includes detailed test results, browseable screenshots of apps running on real physical devices, performance monitoring, and detailed device logs and stack traces to help developers find and fix bugs quickly.
You will capture snapshots of the application stack traces while the client load test is submitting requests.
The stack trace shows you what line of Java code is executing in each thread and which method called it (see http://developer.
Runtime Error Analysis adding explanations and solution suggestions to Java stack traces
Automatic population of task contexts from stack traces present in defects.
Features in Great Circle Enterprise will include: - Memory error reporting with full symbolic stack traces which link directly to source code - Third-party and legacy code error detection and correction - Multiple free detection and reporting - Memory corruption reporting - Heap profiling - Remote debugging capabilities - High-performance, non-fragmenting memory allocation - High-performance garbage collection for C/C++ programs - High-performance SMP parallel memory management - Low memory simulation for testing in memory-limited environments - Web-based graphical user interface
Drill down into bad requests: hotspots in code, stack traces for errors, and stalled requests
A new feature in the console displays real time stack traces so that users can watch the stack change.
Additional features of JetBrains ReSharper UnitRun include: * Progress Bar and Diagnostics View display the progress and overall status of the test being run * Easily identify console output and exception stack traces produced by a selected test or all tests * Monitor precise time measurements for tests
A sudden flood of support tickets, failed web requests, application server errors and stack traces can cause serious application failures.