Bug 527138 - Starting gdbserver from CDT sometimes stalls indefinitely

- fix RunConsole.attachToTerminal to verify that any finishDate
  is not before the start date
- also add a pause before attempting to attach as well as an
  additional check to ensure that the Container is running
- add a log of any error that occurs and notify all console
  listeners with a zero-length string that there will be no more
  output
- add similar logic to attachToConsole except for the console
  listener stuff which isn't applicable

Change-Id: Idc091b24c071228d2fdb4592d3595ba483297a5d
Reviewed-on: https://git.eclipse.org/r/111410
Tested-by: Hudson CI
Reviewed-by: Jeff Johnston <jjohnstn@redhat.com>
1 file changed
tree: 75bd68a8ed964a06a19a3cd6c73e68b3d979d92a
  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!