Search Results for "without code"

Shadowsocks-libev is a lightweight secured SOCKS5 proxy for embedded devices and low-end boxes. Shadowsocks-libev is written in pure C and depends on libev. It's designed to be a lightweight implementation of shadowsocks protocol, in order to keep the resource usage as low as possible. Snap is the recommended way to install the latest binaries. You can build shadowsocks-libev and all its dependencies by script. The latest shadowsocks-libev has provided a redir mode. You can configure your...

...The MCP server then loads this captured “flow” and exposes it to the AI agent via the Model Context Protocol (MCP), letting the agent examine, search, filter, and reason about the session just as a human developer would, without needing the agent to re-run the flow or rely on minimal reproduction data (logs, screenshots).

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/

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

...Instead of manually adding logging statements everywhere, you simply annotate a method and Hugo injects the logging at compile-time in debug builds, keeping release builds clean. This helps developers gain visibility into method flows, execution timing, and parameter passing without cluttering production code. The annotation doesn’t remain in the compiled class for non-debug builds, so there’s zero runtime penalty in release. Hugo uses bytecode/annotation processing behind the scenes but maintains simple API usage for developers. It’s especially useful during development and debugging phases in large Android codebases where tracing logic by hand would be tedious.

This is a student project designed to compete in the 2010 IEEE Computer Society Student Competition: http://www.computer.org/portal/web/competition/2010competition The Code Red architecture is designed for extremely lower power environments, like distributed sensor networks. Included is a design of that architecture, a Java-based simulator, an implementation (without vector instructions) designed as a Logisim circuit (http://ozark.hendrix.edu/~burch/logisim/), and more. The name "Code Red" comes from our team name, the Red Team. ...

...It’s also useful for forensic snapshots: enumerate objects of a certain type, find reference cycles, or measure memory pressure without pre-instrumentation. While powerful, it’s designed for careful, auditable use—showing exactly what code runs and where—so teams can regain visibility when black-box processes go sideways.

Glassbox is an automated troubleshooting and monitoring agent for Java apps that diagnoses common problems with one-click. Drop in a .war file from http://www.glassbox.com and find out what's wrong with your existing web apps, without any code chang

Easy to use Java utility to collect method level performance data for any Java applications without modifying its code.

ALF, The Automated Logging Framework, is a native logging framework for Java with the unique advantage of supporting automated method tracing. This platform-independent library allows developers to debug their applications quickly without adding code