A powerful disassembler and a versatile debugger IDA Pro as a disassembler is capable of creating maps of their execution to show the binary instructions that are actually executed by the processor in a symbolic representation (assembly language). Advanced techniques have been implemented into IDA Pro so that it can generate assembly language source code from machine-executable code and make this complex code more human-readable.
The debugging feature augmented IDA with the dynamic analysis. It supports multiple debugging targets and can handle remote applications. Its cross-platform debugging capability enables instant debugging, easy connection to both local and remote processes and support for 64-bit systems and new connection possibilities.
Based on our record, VisualVM should be more popular than IDA. It has been mentiond 21 times since March 2021. We are tracking product recommendations and mentions on various public social media platforms and blogs. They can help you identify which product is more popular and what people think of it.
The tool used in those white screenshots is called IDA pro, a decompiler. https://hex-rays.com/ida-pro/. - Source: Hacker News / 2 months ago
Learn assembly and then fuck around with https://hex-rays.com/ida-pro/. Gonna take you a week max. Source: 6 months ago
To RE the executable IDA Pro can be very useful: Https://hex-rays.com/ida-pro/. Source: over 1 year ago
It’s a good disassembler that is fairly expensive. https://hex-rays.com/ida-pro/. - Source: Hacker News / over 1 year ago
It's a disassembler, widely used for creating, for example, cracks/executable patches for games. https://hex-rays.com/ida-pro/. - Source: Hacker News / over 1 year ago
If you're curious, attach VisualVM and watch the RAM usage graph. You'll notice that Java performs garbage collections long before reaching allocating the maximum amount of RAM allocated, and you can't even feel any performance issue in-game. Source: about 1 year ago
Hangs and deadlocks are significantly harder to debug. A first step is taking a thread dump so you can see what each thread in the JVM is currently trying to do. I like VisualVM for this, you can also use the command-line tools jps -l (to list all Java PIDs) and jstack for taking a thread dump. Source: about 1 year ago
The Java VisualVM project is an advanced dashboard for Memory and CPU monitoring. It features advanced resource visualization, as well as process and thread utilization. - Source: dev.to / about 1 year ago
This sounds like a server thread freeze/deadlock/crash or something. I think I would start debugging this using a tool like VisualVM; attach it to the game, wait for the hang, take a thread dump, and check what the server thread is up to. Source: about 1 year ago
Just wanted to chip in to say that /u/UtilFunction is correct. The proper way to measure memory consumption of any Java application independent of which garbage collector is used is to perform a heap dump (which automatically forces a complete garbage collection). I like to use VisualVM for that. Source: about 1 year ago
Ghidra - Software Reverse Engineering (SRE) Framework
Eclipse Memory Analyzer - The Eclipse Foundation - home to a global community, the Eclipse IDE, Jakarta EE and over 350 open source projects, including runtimes, tools and frameworks.
OllyDbg - OllyDbg is a 32-bit assembler level analysing debugger.
JConsole - Provides information about performance and resource consumption for Java applications.
X64dbg - X64dbg is a debugging software that can debug x64 and x32 applications.
Robot Console - Robot Console is a Message and Event Monitoring Software for IBM i thathas automatic message management, resource monitoring, and log monitoring.