commit | 43e86fff1e2fdf777ed46fe772abb0888dc3bd2c | [log] [tgz] |
---|---|---|
author | Eugene Tarassov <eugenet@xilinx.com> | Sat Jul 24 12:26:19 2021 -0700 |
committer | Eugene Tarassov <eugenet@xilinx.com> | Sat Jul 24 12:26:19 2021 -0700 |
tree | 08ece1235e12bb6147b52c49b91fd06f40dc3aab | |
parent | 4189408e030dde2853a3df3a80571dd43cb8e798 [diff] |
TCF Agent: added support for one-to-many file path mapping
TCF is a vendor-neutral, lightweight, extensible network protocol mainly for communicating with embedded systems (targets). On top of the protocol specification, which is the core of TCF, the project includes a plain-C implementation of a lightweight extendable target agent, Java client API (usable stand-alone or on top of Eclipse), Python and Lua client APIs, complete debugger UI implementation in Eclipse, integration with CDT, Target Explorer, documentation and usage examples.
agent : The reference agent, implementing debug related services e.g. Memory, RunControl, Registers, Stacktrace, Breakpoints, Symbols, LineNumbers, Expressions.
docker : Dockerfile image for host and cross builds of the debug agent.
examples : Implementation of a daytime service.
server : A proxy server sitting between the client on the host and an agent running/embedded on the target as part of the firmware or RTOS. It implements Symbols and LineNumbers services.
tests : Standalone tools for testing (e.g dwarf, extended commandline client)