| commit | c8df5ca8eca21df1968e2cd2b624a316d256cfbc | [log] [tgz] |
|---|---|---|
| author | Eugene Tarassov <eugenet@xilinx.com> | Wed Aug 11 13:14:59 2021 -0700 |
| committer | Eugene Tarassov <eugenet@xilinx.com> | Wed Aug 11 13:14:59 2021 -0700 |
| tree | 6ec7ebfd228482236f1c7910019781a740953242 | |
| parent | 43e86fff1e2fdf777ed46fe772abb0888dc3bd2c [diff] |
TCF Agent: DWARF 5: fixed location list base address From DWARF 5 standard, section 2.6.2, if there is no preceding base address entry, then the applicable base address defaults to the base address of the compilation unit.
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)