EDT Debug Tracer

Install

Manual install

git clone https://github.com/lytkinam/edt-debug-tracer
cd edt-debug-tracer
javac --release 17 -d plugin/bin -cp "$CP" plugin/src/plugin17/test/*.java
jar cfm plugin17-test_1.0.0.jar plugin/META-INF/MANIFEST.MF -C plugin/bin .

This is third-party code. Review the repository files before installing.

What it does

The plugin intercepts Eclipse Debug API events during a 1C:EDT debug session and, at every step, records the procedure, line, module, thread, call stack and variables into SQLite and JSON. The same HTTP port serves a JSON-RPC 2.0 endpoint at /mcp with eight tools: debug status, step, resume, suspend, wait for break, stack frame variables, and the full call stack. It also manages breakpoints, which can be placed automatically from an already recorded trace. There is a ready integration pattern for Vanessa: the trace records around each BDD step, and the result can be attached to an Allure report.

Who it is for. For 1C developers and testers who debug configurations in EDT and want to give an agent programmatic access to the debug session and execution trace.

Example request

Start debugging, wait for the first breakpoint and show me the call stack and variables of the current frame

Limitations

The plugin only works while EDT is attached to a debug session as the debug target; without one the trace buffer stays empty. It is built from source manually for a specific Eclipse or EDT build, with no ready installer. It is a single-author project, and part of the documentation reads as a development log with an AI agent rather than a reference for an outside user.

How to disable. Remove the plugin jar from the Eclipse or EDT plugins folder, delete its registration line from bundles.info and restart Eclipse.

MCP

Transport

http

Authentication

not required

Security check

• Controls a live debug session: can step, resume and suspend execution threads
• The plugin's HTTP server listens on a local port with no authorization by default

README in short

The README lists the plugin's features: intercepting debug events, 12 fields per trace step, dual SQLite and JSON storage, 17 HTTP endpoints, automatic breakpoint placement from the trace, around 130 config parameters, and trace post-processing with a Python script. It gives Eclipse build commands, a sample tracer.properties config, a grouped endpoint table, the step record format, a target usage scenario, an architecture diagram and a version history from v1.0 to v9.2. MIT license.

Related