Search Results for "dump process java"

StackTraceSealer is a JConsole plugin with its own Java Agent Library that can be used to seal stack frames on a thread stack trace to detect whether these frames have changed or they have remained the same all the time to aid in finding an infinite loop on a production system when all you have is a long seemingly constant stack trace in the thread dump.

Libinstrument is a complete and easy way to do custom function instrumentation for C/C++. The project comes ready with classic applications of instrumentation, such as AOP (Aspect Oriented Programming), Concern and Side Effect injection, stack tracing, exception tracing, basic time profiling, callgraph profiling and other. A GC (Garbage Collector) module is also under development. Libinstrument is highly portable and decoupled. The project comes with a CMake build system, integration with...

CrashLog is a crash report platform for Android developer, helping developers to quickly locate problems.

(Diver is in the process of being moved to GitHub. Please find us at https://github.com/thechiselgroup/Diver. Support requests & messages sent here may never be seen.) Dynamic Interactive Views For Reverse Engineering. Div/er is a set of Eclipse Plugins that aid developers in understanding software. It uses dynamic analysis and reverse engineering to offer views and filters that aid comprehension and discovery.

This is a research project aimed at providing tools to help developers capture and visualize what is actually happening when your program executes. And hopefully make debugging an easier, quicker and less painful process.

A collection of tools that should help you to analyze java thread dumps. MOVED TO github: https://github.com/slotties/jtdutils

A front end of any dump analyzer ,its purpose to assist developers to analyze dumps generated by processors and find the reason of crash.

It is a Process Monitoring Toolkit with the ability of Extend. E.g. You can use it to monitor a specified process. And set a triger like (over 50MB mem use) then do something like (report to DB).

A facility to keep a history of context information during runtime and then dumping it in a separate file when a problem occurs (similar to core dump).