Search Results for "cdm-core"

YARI is a comprehensive tool suite to debug (layouts), spy, spider, inspect and navigate SWT and Eclipse based application GUIs (Workbench or RCP) at runtime.

Node.js Debugging Guide is a Chinese-language technical book and repository about diagnosing performance, memory, code, and production problems in Node.js. Its CPU section introduces Linux perf, FlameGraph, V8 profiling, and the Tick Processor. Memory chapters cover core dumps, llnode, heap snapshots, leak detection, and CPU or memory monitoring. Code-level material examines promises, async and await, stack traces, the event loop, native Rust add-ons, and uncaught exceptions. Tooling lessons use source maps, Chrome DevTools, Visual Studio Code, debugging modules, REPL utilities, and hot reload. Additional chapters cover New Relic, Elastic APM, ELK, Jaeger, Sentry, Telegraf, InfluxDB, Grafana, Node Clinic, and AliNode. ...

A complete Lua solution is written entirely in C# for the .NET, Mono, Xamarin and Unity3D platforms. Support for the complete Lua standard library with very few exceptions (mostly located on the 'debug' module) and a few extensions (in the string library, mostly). Supports dumping/loading bytecode for obfuscation and quicker parsing at runtime. An embedded JSON parser (with no dependencies) to convert between JSON and Lua tables. Easy opt-out of Lua standard library modules to sandbox what...

...By parsing a core dump file or a live process's memory, core analyzer is able to scan the target's heap data for memory corruption, search the whole address space for data object's references, or analyze memory pattern. It is thorough, labor-free, and insightful. I use the tool on daily basis and it is proved to be invaluable to debug many tough issues.

mspgcc4 is no longer supported. Please use the newer toolchain at the MSPGCC project. (This was a port of the GCC 4.x branch to the Texas Instruments MSP430 microcontroller core. It is based on the MSPGCC project that is stuck with GCC 3.2.3.)

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).