| commit | bb4dbcd2f00d7e70bb40a26fc8021abdaaee7ef1 | [log] [tgz] |
|---|---|---|
| author | Eugene Tarassov <eugenet@xilinx.com> | Wed Nov 03 10:42:10 2021 -0700 |
| committer | Eugene Tarassov <eugenet@xilinx.com> | Wed Nov 03 12:55:09 2021 -0700 |
| tree | 87924abe3d1b8e14bc7430f152f1dfe026d330ed | |
| parent | c4babeebdb86c7b546b63f358fbca46015d70fe2 [diff] |
Bug 577001 - DW_AT_high_pc with DW_FORM_udata form not handled Handling of relocatable FORM_DATAn changed to be more generic
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)