| tag | 3210cd0cb88ee1c7509744b3f4202031f2831ad8 | |
|---|---|---|
| tagger | Bernd Hufmann <Bernd.Hufmann@ericsson.com> | Wed Sep 28 12:05:39 2016 -0400 |
| object | ffbdc899a294d72c56557c80e0e974a3dd14b23a |
Trace Compass 2.1.0 release
| commit | ffbdc899a294d72c56557c80e0e974a3dd14b23a | [log] [tgz] |
|---|---|---|
| author | Marc-Andre Laperle <marc-andre.laperle@ericsson.com> | Tue Sep 13 18:08:21 2016 -0400 |
| committer | Marc-Andre Laperle <marc-andre.laperle@ericsson.com> | Wed Sep 14 10:59:22 2016 -0400 |
| tree | ba08ea01eb9c6c2c6ecbc60e34926c8933401d22 | |
| parent | 0975e5e206869cd7c9f863db72a612d8adaeccae [diff] |
tmf: Fix hang in TarInputStream.skipToEntry when importing large tar.gz When importing a large tar.gz archive, it can hang in TarInputStream.skipToEntry. Depending on the size of the entries in the Tar and the order in which they are read, it is possible that bytesread will overflow and become negative. Because of that, the code that skips bytes fails to skip properly and enters in an infinite loop. This patch fixes the issue by making the bytesread a 'long'. Because this class is in the platform, several files had to be copied over in order to get the fix right away. Those files will be removed once the fix is in the platform and that the fix is released. Bug: 501379 Change-Id: Ia1613da08715968f23a803519a2e78aa7c51482f Signed-off-by: Marc-Andre Laperle <marc-andre.laperle@ericsson.com> Reviewed-on: https://git.eclipse.org/r/81053 Reviewed-by: Hudson CI Reviewed-by: Bernd Hufmann <bernd.hufmann@ericsson.com> Tested-by: Bernd Hufmann <bernd.hufmann@ericsson.com>
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 viewing GDB traces lttng/ | LTTng integration pcap/ | libpcap integration rcp/ | Code specific to the RCP version 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.
To set up the environment to build Trace Compass from within Eclipse, see this wiki page: http://wiki.eclipse.org/Trace_Compass/Development_Environment_Setup
The Maven project build requires version 3.3 or later. It can be downloaded from http://maven.apache.org or from the package management system of your distro.
To build the project manually using Maven, simply run the following command from the top-level directory:
mvn clean 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:
mvn clean 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.
The following Maven profiles 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 various versions of the Eclipse platform. Available 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.
-Pctf-grammar
Re-compiles the CTF grammar files. This should be enabled if you modify the .g files in the ctf.parser plugin.
-P -build-rcp
Disables the “build-rcp” profile to skip building the RCP archives.
-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. Must be used with -Pbuild-rcp!
-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).
