Bug 553627 - gmon.out generated on target board is failing due to EOF

- add 64 suffix check in GmodDecoder constructor

Change-Id: Ic9aacf7c866bf3710443442257a3b4309d5892eb
Reviewed-on: https://git.eclipse.org/r/153671
Tested-by: Linux Tools Bot <linuxtools-bot@eclipse.org>
Reviewed-by: Jeff Johnston <jjohnstn@redhat.com>
(cherry picked from commit abe3b9a551599aa1080d6b053cca3d2f3fdc8eb7)
Reviewed-on: https://git.eclipse.org/r/153676
1 file changed
tree: 3eb81a92046a8b4e3f0e2c73c918e84774a971ef
  1. changelog/
  2. containers/
  3. gcov/
  4. gprof/
  5. javadocs/
  6. libhover/
  7. lttng/
  8. man/
  9. oprofile/
  10. perf/
  11. profiling/
  12. releng/
  13. rpm/
  14. systemtap/
  15. vagrant/
  16. valgrind/
  17. .gitignore
  18. .project
  19. pom.xml
  20. 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!