Search Results for "tiny core linux"

DiDasm is a small and fast disassembler, useful for Windows kernel developers. Advantages: - highly portable, has minimal runtime requirements (C runtime); - core libraries do not require any external components; - includes instructions emulator (diana_processor); - has stream oriented design; Supported platforms: i386, amd64 Supported instructions: x586/amd64/FPU/MMX/SSE/SSE2

For C (and CPP obviously): Include a fast and tiny RAM-tracing feature for Real-Time (RT) debugging purposes. >> ONLY FOR DEBUGGING << Very much faster than printf-debugging, which may result in unforseen results in an RT environement.

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

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

MSPDebug is a free debugger for use with MSP430 MCUs. It supports FET430UIF, eZ430, RF2500 and Olimex MSP-JTAG-TINY programmers. It can be used as a proxy for gdb or as an independent debugger with support for programming, disassembly and reverse eng

The project is now hosted on github: https://github.com/yanqi27/core_analyzer.git Core analyzer is a power tool to debug memory issues. With ever increasing complexity and dataset size of application programs, it is very challenging to find the root cause of a memory bug. Programmers often use debugger to go through many contexts or data objects in order to hunt down a suspicious variable or object. However, the task is boring, prone to error and usually fruitless. By parsing a core dump...

It reads windows Portable Executable file format. DLL & EXE . Coming up with support for name de-mangling Portable Tested on Linux/ SunOS/ Windows - VS10 / Mac You might also want to check https://sourceforge.net/projects/core-dump-analyzer

A tiny and easy to use log library for C/C++. Written in C. Customizable log message format for global and specified output target Cross platform support. Tested: linux, win32, wince, mac

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

Cross-Crash is an enhancement to the existing Crash utility that analyzes the linux kernel core dumps by Linux Kernel Crash Dump (LKCD). It allows the analysis of core dumps on hosts that are not of the same architecture the dumps were originated from.

A neat tool for creating GDB readable coredumps from multithreaded applications -- while the program is running. The coredumper library can be compiled into applications to create core dumps of the running program, without terminating.

CDK4NIOS stands for Cross Development Kit for Altera's soft core processor NIOS and should you support with a comprehensive Assembler and C/C++ development environment under Linux. It will present only free of fee tools, so you can use it without risks.

WrapLog is a tiny Java logging package that can "wrap" around other logging packages, thus removing the need to stick to a certain one. This is particular useful for Java libraries that want to leave the choice for a logging packing to the client code.

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

[from port's pkg-descr] "pstack" is a workalike for the Solaris program of the same name. Running pstack on a process or core file produces a stack trace of each thread in that process.