Search Results for "user interface"

Reko decompiler reads program binaries, decompiles them, infers data types, and emits structured C source code. Designed with a pluggable architecture, it currently has: - support for 68k, ARM, MIPS, PowerPC, Risc-V, Sparc, x86, Z80 processors and many more - support for EXE, Elf, AmigaOS Hunk executable formats and many more - support for MS-DOS, Win32, U*ix, AmigaOS , C64, ZX-81 Reko decompiler comes with a GUI and a command-line interface. Visit https://github.com/uxmal/reko...

Visualizer is a tool for .NET developers who use MS Visual Studio. In debug mode, it provides the ability to view and search objects of type String, StringBuilder, DataTable and Image, by clicking on the magnifying glass. Install by copying all files in the zip to your user folder: C:\Users\<username>\Documents\Visual Studio 2012\Visualizers\

Tiny8051 is small 8051 microcontroller simulator written in C#. Project was created for educational purposes, to show how µP works by using clean visual interface and debugging. Note: communication over serial port was not implemented, because there was no demand for it.

ClrDbg can open a dmp file, or connect to a running process, and display information about the objects on the heap and their class information (such as field definitions and method signatures), threads and their call stacks. ClrDbg uses the Microsoft.Diagnostics.Runtime.dll (ClrMD). The user-interface allows the user to drill-down by clicking on hyperlinks in a grid view.

LuaEdit is an IDE/Text Editor/Debugger for the Lua language. Its interface looks like MS Visual Studio .Net� and includes syntax highlighting, code completion, advance breakpoint management, efficient search engines, etc. Client under GPL and server (core debugger) under LGPL.

Tool for monitoring of OCI client applications [f.e.: TOAD/TOra, or any OCI-based fat client] interaction with Oracle Database. Monitors SQL statements and values passed/fetched between client application and RDBMS. Consists of simple and nice GUI [C#] and events handler [C++] with quite a lot of OCI hacking. Interface between handlers and tool's GUI is through tailing of XML "pipeline" files in $HOME/.ocimonitor directory. Tool is quite similar to Quest SQLMonitor, which is unable to trace values.

Visual Studio Add-In where developers can arrange their breakpoints via Drag'n'Drop in a tree structure to model a path of execution.