From ab2796793ac96e9c2555881b9aa521a51645b6bd Mon Sep 17 00:00:00 2001 From: eutarass Date: Sat, 6 Sep 2008 01:17:15 +0000 Subject: TCF Agent: Got rid of libelf dependency. Use mmap() to access ELF sections data. --- docs/TCF Getting Started.html | 21 +++++---------------- 1 file changed, 5 insertions(+), 16 deletions(-) (limited to 'docs') diff --git a/docs/TCF Getting Started.html b/docs/TCF Getting Started.html index 287b11c05..02a6afc55 100644 --- a/docs/TCF Getting Started.html +++ b/docs/TCF Getting Started.html @@ -125,18 +125,9 @@ below are steps to create and populate Eclipse workspace with TCF projects:

Linux is the recommended evaluation platform, since most TCF services are implemented. To build the agent:

On Windows, SysMonitor service is not implemented, so RSE Processes demos will not work. @@ -212,8 +203,7 @@ It also extends Processes subsystem to include CPU utilization data and some oth

Using TCF With Eclipse Debugger

Plugins org.eclipse.tm.tcf.debug and org.eclipse.tm.tcf.debug.ui allow to start a debug session -by connecting to a machine runnning TCF agent. This is not a complete debugger implementation, it is intended for -demo and reference purposes. +by connecting to a machine runnning TCF agent.

To start a debug session over TCF:

-

In TCF debug session only "Debug", "Breakpoints" and "Registers" views are populated. Source level debugging -in not supported at this time. Breakpoints can be planted at an absolute addresses only, using menu command "Run/Toggle Breakpoint". -"Registers" view can be brought in by "Window > Show View > Registers". Registers can be shown only for top stack frame. +

In TCF debug session "Debug", "Breakpoints", "Registers", "Variables" and "Expressions" views are populated. +Source level debugging is fully supported if the source code can be found in a CDT project in current workspace.

-- cgit v1.2.3