Search Results for "call graph"

MiniChain is a small Python library for building applications that combine large language models, prompts, and executable tools. Developers annotate ordinary functions to define model calls while keeping prompt templates separate from application logic. Multiple functions can be chained so the output of one model or tool becomes the input to another. The library records calls as a graph, making intermediate steps easier to inspect, debug, and retry. It includes model abstractions for...

Pinject is a lightweight dependency-injection library for Python that favors explicit wiring and testability over magic. Instead of global singletons, you declare providers (bindings) that describe how to construct objects, and Pinject resolves the graph by inspecting call signatures. Its container supports constructor injection and fine-grained scoping so you can share expensive resources while keeping tests isolated. The library leans on Python’s introspection to minimize boilerplate, making it natural to adopt in codebases that already rely on type hints or keyword arguments. ...

A COBOL debugger for GnuCOBOL written in GnuCOBOL. Works with both current GnuCOBOL and old GnuCOBOL/OpenCOBOL 1.1; could be used for other vendors with slightly modifications, too. Take a look at https://gnucobol.altervista.org/tp-cobol-debugger/

Twiggy is a specialized code size profiler designed for analyzing WebAssembly (Wasm) binaries, helping developers understand why their compiled output is large and how different functions contribute to that size. It works by inspecting a binary’s call graph and providing detailed breakdowns of which functions are included and how they are interconnected, allowing developers to trace dependencies and identify unnecessary code paths. This makes Twiggy particularly useful in performance-sensitive environments such as web applications, embedded systems, and blockchain smart contracts, where minimizing binary size is critical. ...

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

Shiny is a lightning fast, fully documented & by-far-easiest-to-use C/C++/Lua profiler with no extensive surgery. Results are smoothed & shown in run-time as a call-tree or sorted-by-time. Output also renderable as graphs in Ogre3D or your custom engine

https://github.com/jplevyak/ifa IFA, Iterative Flow Analysis is a combined data-flow and control flow analysis. It is capable of resolving the concrete types (as opposed to the nominal or declared types) and the interprocedural call graph for statically or dynamically typed programs.

KCachegrind visualizes traces generated by profiling, including a tree map and a call graph visualization of the calls happening. It's designed to be fast for very large programs like KDE applications.

The project's aim is to develop a fast Method Call Graph generator for the Java Programming Language. The search proceedure combines a Finite State Machine and ad hoc parsing to allow for fast access to method definitions and method calls within the source code.

FunctionCheck is a profiler for C/C++ programs, based on gcc V4.6.3+. Features are flat profile, cycles detection, call-graph, MIN/MAX time in functions, memory profiling, profiling control at execution...

hlv is a collection of high level view plugins for eclipse. A the moment it will just be a call graph view using the zest toolkit and GEF.

Cflow2vcg convert the result of the cflow utility in a VCG format. It offers the ability to view graphically the call-graph of sources, and import it in documentation.

Given a GCC "gmon.out" file (or output from the GNU tool gprof), generate an HTML version with one page per call graph, including hyperlinks and (later) graphical analysis.

This tool converts the output of gprof to a format processible by the DOT tool, to generate a nice graphical function call graph.

Functrace is a tracing facility, similar to ltrace/strace, that can be used for tracing the dynamic call graph internal to a running program (i.e. a trace of function calls).

MSP430static is a tool for the analysis of MSP430 firmware images, such as those produced by TinyOS and mspgcc. Features include call-graph generation, recovery of library symbol names, and easy extensibility in Perl or SQL.