commit | 19452a3606a76ecaac8164c585ec0c4f055d9351 | [log] [tgz] |
---|---|---|
author | Eugene Tarassov <eugenet@xilinx.com> | Thu Mar 11 17:14:34 2021 -0800 |
committer | Eugene Tarassov <eugenet@xilinx.com> | Thu Mar 11 17:14:34 2021 -0800 |
tree | e0c47774db6cec3b35f7afe8f0a9d759616cd1ea | |
parent | ed1ae9910da5dba28e0e4b7ce161442af719b86a [diff] |
TCF Tests: fixed handling of function with code ranges
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)