Skip to main content
path: root/docs
diff options
authoreutarass2008-09-06 01:17:15 +0000
committereutarass2008-09-06 01:17:15 +0000
commitab2796793ac96e9c2555881b9aa521a51645b6bd (patch)
tree0e44dd735371c28b21e11b32b2373f9be862b690 /docs
parent5ba285d9ccccec48c35297edf5463a3e256ebc60 (diff)
TCF Agent: Got rid of libelf dependency. Use mmap() to access ELF sections data.
Diffstat (limited to 'docs')
-rw-r--r--docs/TCF Getting Started.html21
1 files changed, 5 insertions, 16 deletions
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:</p>
<p><b>Linux</b> is the recommended evaluation platform, since most TCF services
are implemented. To build the agent:
- <li>Make sure <code>elfutils-libelf-devel</code> is installed.
- On Fedora, it can be installed by command:
- <pre>yum install elfutils-libelf-devel</pre>
- It also can be built and installed from source code, e.g.
- <a href=""></a>:
- <pre>
- ./configure
- make
- make install
- setenv LD_LIBRARY_PATH /usr/local/lib:$LD_LIBRARY_PATH</pre>
<li>Run <code>make</code> command in <code>&lt;TCF Root&gt;/agent</code> directory.
- <li>Start agent with <code>./agent</code> command.
+ <li>Start agent with <code>./agent -L- -l0</code> command.
+ Use other -l option values to increase agent log details level.
<p>On <b>Windows</b>, 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
<h2><a name='Debugger'>Using TCF With Eclipse Debugger</a></h2>
<p>Plugins <b></b> and <b></b> 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.
<p>To start a debug session over TCF:</p>
@@ -229,9 +219,8 @@ demo and reference purposes.
<li>Press "Debug" to start the debugger.
-<p>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.
+<p>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.

Back to the top