Google Git
Sign in
eclipse / gerrit / linuxtools / org.eclipse.linuxtools / 637e48106758e0b815e39bfe97a9532da2b7e453
commit637e48106758e0b815e39bfe97a9532da2b7e453[log] [tgz]
authorJeff Johnston <jjohnstn@redhat.com>Fri Aug 31 16:15:44 2018 -0400
committerJeff Johnston <jjohnstn@redhat.com>Fri Aug 31 16:55:40 2018 -0400
tree2b9dca20852bed03492fc735dbafbe46d805a80c
parentd3b17fe579879895200a3beef65abdee04a7378b [diff]
Bug 538494 - NullPointerException in PerfCore.getHostName

- fix PerfCore getHostName() to check that project URI exists
  before accessing
- add warning message if URI doesn't exist

Change-Id: Iff242a0a70f4d75358e435593683900e8fa501c5
Reviewed-on: https://git.eclipse.org/r/128479
Tested-by: CI Bot
Reviewed-by: Jeff Johnston <jjohnstn@redhat.com>
3 files changed
tree: 2b9dca20852bed03492fc735dbafbe46d805a80c
  1. changelog/
  2. containers/
  3. gcov/
  4. gprof/
  5. javadocs/
  6. libhover/
  7. lttng/
  8. man/
  9. mylyn/
  10. oprofile/
  11. perf/
  12. profiling/
  13. releng/
  14. rpm/
  15. systemtap/
  16. vagrant/
  17. valgrind/
  18. .gitignore
  19. .project
  20. pom.xml
  21. README.md
README.md

Contributing to Linux Tools

Thanks for your interest in this project.

Project description:

The Linux Tools project aims to bring a full-featured C and C++ IDE to Linux developers. We build on the source editing and debugging features of the CDT and integrate popular native development tools such as the GNU Autotools, Valgrind, OProfile, RPM, SystemTap, GCov, GProf, LTTng, etc. Current projects include LTTng trace viewers and analyzers, an RPM .spec editor, Autotools build integration, a Valgrind heap usage analysis tool, and OProfile call profiling tools. The project also provides a place for Linux distributions to collaboratively overcome issues surrounding distribution packaging of Eclipse technology. The project produces both best practices and tools related to packaging. One of our features is a source archive of the Eclipse SDK that can be used by all Linux distributions building and distributing it.

Developer resources:

Information regarding source code management, builds, coding standards, and more.

Contributor License Agreement:

Before your contribution can be accepted by the project, you need to create and electronically sign the Eclipse Foundation Contributor License Agreement (CLA).

Contact:

Contact the project developers via the project's “dev” list.

Search for bugs:

This project uses Bugzilla to track ongoing development and issues.

Create a new bug:

Be sure to search for existing bugs before you create another one. Remember that contributions are always welcome!