commit | acb889e9e397a3ab7dfbd39f6bb577481b10e724 | [log] [tgz] |
---|---|---|
author | Eugene Tarassov <eugenet@xilinx.com> | Mon Dec 28 14:27:42 2020 -0800 |
committer | Eugene Tarassov <eugenet@xilinx.com> | Mon Dec 28 14:27:42 2020 -0800 |
tree | 7f8f9a8794a58e8b787fb73195ba7cd974ce84c4 | |
parent | 9f7a9847fc84cc732b0e277920b0c74142619ca2 [diff] |
TCF Agent: Fixed computation of run-time addresses of symbols from a separate debug info file In the latest debug info files, program headers are not valid and should not be used to compute run-time addresses
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)