tracecompass - Archived Mirror of the main Trace Compass git repo

项目说明

This is moved to

Eclipse Trace Compass
=====================

This source tree contains the source code for the Trace Compass plugins for
Eclipse.

The plugins are categorized as follows:

analysis/ | Generic extensions to the base framework
btf/ | Best Trace Format (BTF) integration
common/ | Generic utilities that can be used by other plugins
ctf/ | Common Trace Format (CTF) reader library
doc/ | Documentation and code examples
gdbtrace/ | Support for reading and GDB traces
lttng/ | LTTng integration
pcap/ | libpcap integration
rcp/ | Code specific to the RCP
releng/ | Releng-related plugins
statesystem/ | State System library
tmf/ | Core framework

See the components.svg file for a diagram showing the dependencies between the
different components.

Setting up the de en
--------------------------------------

To set up the en to build Trace Compass from within Eclipse, see this
wiki page:
<

Compiling manually
------------------

The Ma build requires 3.3 or later. It can be downloaded from
< or from the package management system of your distro.

To build the project manually using Maven, simply run the following command from
the top-le:

m install

The default command will compile and run the unit tests. Running the tests can
take some time, to skip them you can append -Dmaven.test.skip=true to the
mvn command:

m install -Dmaven.test.skip=true

Stand-alone application (RCP) packages will be placed in
rcp/org.eclipse.tracecompass.rcp.product/target/products.

The p2 update site, used for installation as plugins inside Eclipse, will be
placed in releng/org.eclipse.tracecompass.releng-site/target/repository.

To generate the javadoc from the Trace Compass source code, run the following
command from the top-le:

m package javadoc:aggregate

The javadoc html files will be under target/site/apidocs.

Tracing Trace Compass
---------------------

Trace Compass can be traced by doing the following in the launch configuration:

* (java 8 only) -
* -Djava.util.logging.config.file=%gitroot%/logging.properties (where %gitroot% is the directory tracecompass is checked out to)
* -Dorg.eclipse.tracecompass.logging=true

Additionally the folder the trace is being written to (default is home/.tracecompass/logs) needs to be created in advance. After running Trace Compass, a trace_n.json will be created in the tracing folder. It needs to be con to true json, so use the jsonify.sh script in the root directory to convert it. Then it can be loaded into Trace Compass, if the Trace Event format is installed from the incubator, or from a web browser such as Chromium.

The performance impact is low enough as long as the log level is greater than "*FINEST*".

NOTE: thread 1 is always the UI thread for Trace Compass. Also, the thread numbers are the J and do not correspond necessarily to Process IDs.

Ma and properties
-----------------------------

NOTE: if you want to build the RCP with older platforms than 4.12 you need to
copy the legacy tracing.product:
cp rcp/org.eclipse.tracecompass.rcp.product/legacy/tracing.product rcp/org.eclipse.tracecompass.rcp.product/

The following Ma and properties are defined in
the build system. You can set them by using -P[profile name] and
-D[property name]=[value] in mvn commands.

* -Dtarget-platform=[target]

Defines which target to use. This is used to build against of
the Eclipse platform. A ones are in
releng/org.eclipse.tracecompass.target. The default is usually the latest
stable platform. To use the staging target for example, use
-Dtarget-platform=tracecompass-eStaging.

* -Dskip-tc-core-tests

Skips the automated core tests. Not required when using
-Dmaven.test.skip=true or -DskipTests=true , which already skips
all the tests.

* -Dskip-short-tc-ui-tests

Skips the short UI integration tests. Not required when using
-Dmaven.test.skip=true or -DskipTests=true, which already skips
all the tests.

* -Dskip-long-tc-ui-tests

Skips the long UI integration tests. Not required when using
-Dmaven.test.skip=true or -DskipTests=true, which already skips
all the tests.

* -Dskip-rcp

Skips building the RCP archives and related deployment targets. Only works in
conjunction with -Dskip-tc-long-ui-tests, due to a limitation in Maven.

* -Pctf-grammar

Re-compiles the CTF grammar files. This should be enabled if you modify the
.g files in the ctf.parser plugin.

* -Prun-custom-test-suite

Runs a test suite present in releng/org.eclipse.tracecompass.alltests. The
test suite to run has to be defined by -DcustomTestSuite=[name], for example
-DcustomTestSuite=RunAllPerfTests.

* -Pdeploy-rcp

Mainly for use on build servers. Copies the generated RCP archives, as well as
the RCP-specific update site, to the paths specified by
-DrcpDestination=/absolute/path/to/destination and
-DrcpSiteDestination=/absolute/path/to/destination, respectively.

* -Pdeploy-update-site

Mainly for use on build servers. Copies the standard update site (for the
Eclipse plugin installation) to the destination specified by
-DsiteDestination=/absolute/path/to/destination.

* -Psign-update-site

Mainly for use on build servers. Signs all the generated update sites using
the Eclipse signing server.

* -Pdeploy-doc

Mainly for use on build servers. Copies the generated HTML documentation to
the destination specified by -DdocDestination=/absolute/path/to/destination.
Some directories may need to already exist at the destination (or Maven will
throw related errors).

项目信息

开发语言：Java

Star 数：78

技术要点

该项目属于CTF思路方向的开源资源，代码结构清晰，适合安全研究人员学习参考。项目围绕Archived Mirror of the main Trace Compass git repository: https://github.com/eclipse-tracecompass展开，提供了可运行的实现，对理解相关安全机制、工具原理与攻防技术具有较高的研究价值。

从技术实现角度看，此类项目的核心在于对底层原理的深入理解与工程化落地。开发者在研究过程中可以结合官方文档与社区讨论，梳理项目的初始化流程、核心模块职责与数据流转，逐步掌握其中的技术细节与设计思路。

使用与学习建议

1. 下载源码压缩包，解压到本地环境。

2. 根据项目类型准备对应的运行环境与依赖。

3. 按照 README 中的步骤完成配置与部署。

4. 在隔离的测试环境中运行验证，避免影响生产系统。

免责声明

本资源来源于开源社区，仅供安全研究、技术学习与合法授权范围内的攻防演练使用，请勿用于任何非法或侵害他人权益的用途。使用本项目产生的一切后果由使用者自行承担。