Undo previous commits for this test branch

Change-Id: Ic58b99b3350c5ba81df43eceac2b3aeacf7b89fd
Signed-off-by: Marc Khouzam <marc.khouzam@ericsson.com>
Bug 455992 - MIRunControlTest.getExecutionContexts fails when run in
remote mode 

Change-Id: I869a7496e63380f3839d641105fa29fc0c1c3b74
Signed-off-by: Marc Khouzam <marc.khouzam@ericsson.com>
Reviewed-on: https://git.eclipse.org/r/38692
Tested-by: Hudson CI
Revert "Bug 451929 - Leverage p2 ability to express native packages"

This is breaking downstream builds.

This reverts commit 18e6101a53d99969f9dff1fdbc95debb18983390.

Change-Id: I5dd2ee129518757866ab832c683b648d13b07b83
Reviewed-on: https://git.eclipse.org/r/38594
Tested-by: Hudson CI
Reviewed-by: Doug Schaefer <dschaefer@qnx.com>
Typos

Change-Id: I78bd2f2f640dcac283bf0bc4259d6acf3080a3c2
Signed-off-by: Marc Khouzam <marc.khouzam@ericsson.com>
Bug 456083 - Wrong preference scope causes test dependencies

Change-Id: I36b91e6c0c8180919e033d7630db92f148b69214
Signed-off-by: Marc Khouzam <marc.khouzam@ericsson.com>
Reviewed-on: https://git.eclipse.org/r/38721
Tested-by: Hudson CI
Cosmetics.
Adjusted method visibility.
Cosmetics.
Bug 456099 - Renaming a class should also rename related files
Avoid gdb bug in StepIntoSelectionTests for gdb <= 7.3

When a breakpoint is set directly at the start of a function, and you step
into that function, gdb <= 7.3 will generate a "stopped" event with two
reason fields. The first to indicate that the step range ended and the
other to indicate that a breakpoint was hit. While this is not really
correct from gdb to include the same field twice in a single event,
the implementation of MIRunControlEventProcessor_7_0 will generate two
distinct MIStoppedEvent events. This confuses the step-into-selection
mechanism, who will issue two finish/step-return instead of one.

For all gdbs, we will have a test where the breakpoint is a not at the
function entry.

Then, for gdb > 7.3, we will have the same test but with the breakpoint
at the function entry, to test that particular case. This case is known
to be broken with gdb <= 7.3 (rather old) and will stay that way unless
somebody feels like fixing it.

So, for both:

- atDoubleMethodStopAtBreakpoint
- atDoubleMethodSkipBreakpoint

I extracted the code in a common function which takes in parameter the
line to set the breakpoint at.

Change-Id: I2ae4bc527afe0ab195e9b066279ed92f74d652f3
Signed-off-by: Simon Marchi <simon.marchi@polymtl.ca>
Reviewed-on: https://git.eclipse.org/r/38717
Tested-by: Hudson CI
Reviewed-by: Marc Khouzam <marc.khouzam@ericsson.com>
Tested-by: Marc Khouzam <marc.khouzam@ericsson.com>
debug tests: Add runningOnWindows() method to BaseTestCase 

Change-Id: Ic7fd197cdaddf8824ac1ef43261c056678433865
Signed-off-by: Simon Marchi <simon.marchi@polymtl.ca>
Reviewed-on: https://git.eclipse.org/r/38727
Reviewed-by: Marc Khouzam <marc.khouzam@ericsson.com>
Tested-by: Marc Khouzam <marc.khouzam@ericsson.com>
debug tests: Adapt thread name test for platforms that don't support them

gdb only started reporting thread names at version 7.3. On Windows, they
are never reported.

If somebody wants to enhance the check for MAC OS X, feel free to do it!

Change-Id: I9d028b24930b632678941682da65cd51da9e88dd
Signed-off-by: Simon Marchi <simon.marchi@polymtl.ca>
Reviewed-on: https://git.eclipse.org/r/38728
Reviewed-by: Marc Khouzam <marc.khouzam@ericsson.com>
Tested-by: Marc Khouzam <marc.khouzam@ericsson.com>
debug tests: Disable some reverse tests for gdb 7.0 and 7.1

The following tests fail with gdb 7.0 and 7.1:

  - testStopAtMainWithReverse(Restart)?
  - testStopAtOtherWithReverse(Restart)?

The reason is that execution crosses getenv() while recording is
enabled. gdb has some trouble with that, and outputs an error such as:

	warning: Process record ignores the memory change of instruction at address 0x7ffff7de951f because it can't get the value of the segment register.
	warning: Process record ignores the memory change of instruction at address 0x7ffff7de9576 because it can't get the value of the segment register.
	Process record doesn't support instruction 0xfef at address 0x7ffff7a9e5e2.
	Process record: failed to record execution log.

	[process 6993] #1 stopped.
	0x00007ffff7a9e5e0 in strlen () from /lib/x86_64-linux-gnu/libc.so.6

We could either make the test "easier" to make it pass on those gdb
versions, or disable it for those gdb versions. By "easier", I mean just
execute some simple arithmetic instead of some calls to libc.

I think it is counter-productive to reduce the span of the tests just to
make some old gdb versions happy, so I chose to disable it for those.
Actually, the best would be to write a new test which covers less but
passes for all versions.

Change-Id: I98499fbb5c099232bc39dad3906d7348912b89af
Signed-off-by: Simon Marchi <simon.marchi@polymtl.ca>
Reviewed-on: https://git.eclipse.org/r/38735
Reviewed-by: Marc Khouzam <marc.khouzam@ericsson.com>
Tested-by: Hudson CI
Resume threads individually in GDBMultiNonStopRunControlTest.

For older GDBs, we don't support resuming the entire process. The tests
in GDBMultiNonStopRunControlTest were trying to resume the entire
process as a shortcut and it was failing for GDB 7.1 and probably older
ones too.

This change loops over all suspended threads of the process and resumes
them individually.


Change-Id: Ie1056aa9775114c3a0d795a49d87d6efe431785d
Signed-off-by: Marc Khouzam <marc.khouzam@ericsson.com>
Try from 7.0 to 7.8

Change-Id: I52004ccc8010132e24b4ad948bf17745b7cde8a8
Signed-off-by: Marc Khouzam <marc.khouzam@ericsson.com>