commit | b0a78c7f330d583453d6d427f0322f011042208b | [log] [tgz] |
---|---|---|
author | Eugene Tarassov <eugene@largest.net> | Thu Aug 04 17:11:54 2022 -0700 |
committer | Eugene Tarassov <eugene@largest.net> | Thu Aug 04 17:11:54 2022 -0700 |
tree | 5ab3df9f91758eb569fb87ec55c7f7556ec13ae2 | |
parent | 137abb25dd1f753fcfff35ef52a33644cb456ce0 [diff] |
Bug 580489 - failed to handle .debug_rnglists section sometimes
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)