Add some more tests for source path mappings to ensure that the upcoming
change of using gdb's set substitute-path does not regress any issues.
Change-Id: I9067c8859293c3332439679cb1f663e36a4cc34e
Signed-off-by: Jonah Graham <jonah@kichwacoders.com>
This allows specifying the multiplier on the command line and pass
it along to the tests.
Change-Id: I35cb764a6494a0eb98e5e2205a47522935c2b206
Signed-off-by: Marc-Andre Laperle <marc-andre.laperle@ericsson.com>
We can obtain the full path of the executable using
File#getAbsolutePath(). This is much better than the hack that was
actually doing a launch to ask GDB where the binary was.
I cannot explain why I didn't use this in the original implementation.
Change-Id: Ifa0d538919cd0c231547f1f3e9c4b72837df4257
Commit 84a53f8d80 broke this test for an
architecture with fWordSize == 2. The buffer for writing a word went from
length fWordSize to 1, and the expected buffer size of a read as well.
This commit fixes it.
Change-Id: Ie50766031fc7dd8d480f126abc48a6dfd487b9e5
Signed-off-by: Simon Marchi <simon.marchi@polymtl.ca>
- Fix getModelDataForRegisterDataValueInDifferentNumberFormats failure
Nothing seems to set the register we use to do the test to a particular
value. The value happened to be 0. This broke the octal test, because
it assumes that the result starts with a 0, but has characters after
that 0. This is not true when the result is 0. The fix is to set the
register to a know value beforehand (0x1234).
- Fix compareRegisterForMultipleExecutionContexts for slow targets by
adding missing massageTimeout.
Change-Id: I681acdeb08f8e3c2fdaf8dc9cf60801584da4423
Signed-off-by: Simon Marchi <simon.marchi@polymtl.ca>
With gdbserver 7.5, detaching from a process leaves gdbserver hanging
which prevents the next testcase from running.
We therefore disable the two detach testcases for version 7.5 only.
Note that we cannot simply @ignore the testcases since we want to run
them for the local case, even for version 7.5.
Change-Id: Id4b69420abd1218be5eaf2c54a9f44349283edc2
Signed-off-by: Marc Khouzam <marc.khouzam@ericsson.com>
Instead of modifying the source files of the documentation, it's cleaner
to replace the invocation to makeinfo to invoke "true". This will skip
building of all the docs.
Change-Id: I33a8ba7e1932433de48ab98d6cda3fda0bb09143
Signed-off-by: Simon Marchi <simon.marchi@polymtl.ca>
As a safety net, fail if a line tag is defined more than once.
Also, allow calling resolveLineTagLocations more than once for a single
test.
Change-Id: I0832d3d28c4d688c38fd33dfc668b0ec6b8c4ffa
Signed-off-by: Simon Marchi <simon.marchi@polymtl.ca>
The try/catch doesn't add anything. If getStackTrace throws, the test
will fail and will show the useful stack trace.
Change-Id: Icf453ff2ca6c10a32f264fece0f0db9af8049612
Signed-off-by: Simon Marchi <simon.marchi@polymtl.ca>
I used this command to print a summary of the updates:
mvn versions:display-plugin-updates -Djava.net.useSystemProxies | grep "\\->" | sort | uniq
The command reports which maven plugin versions are outdated per cdt project (pom.xml). The extra grep and sort are just to make it display as a short summary.
Change-Id: I6abec0c1d510aac4599fb0d573d443807ee84a7b
Signed-off-by: Marc-Andre Laperle <marc-andre.laperle@ericsson.com>
I got a feedback that the error message when passing an unsupported
version should be more helpful.
Change-Id: I3c925c500d6de787ca9bfce421eda6109e9f6415
Signed-off-by: Simon Marchi <simon.marchi@polymtl.ca>
MIMemoryTest.writeCharVarying{Address,Offset}
When we switched SyncUtil.readMemory to use queries, it exposed a race
condition with the asserts that check for the number of event received.
Basically, nothing guarantees that when the assert is evaluated the
event had the time to arrive.
We now use a ServiceEventWaitor to wait until the event arrives (with a
timeout, of course).
At the same time, rename word_size to wordSize.
Change-Id: I6f4b51e22f46625e20bbbdbac91cf70cfd864e5e
Signed-off-by: Simon Marchi <simon.marchi@polymtl.ca>
There is a superfluous LINE_MAIN_BEFORE_THREAD_START that is causing
problems, remove it.
Change-Id: I57c4637ada0b5efda2848029e5216a13cf638067
Signed-off-by: Simon Marchi <simon.marchi@polymtl.ca>
Re-using the waitor between tests possibly a dependency between tests
(e.g. on the order they are ran). It would be easy to forget to add an
fWait.waitReset() to a test and break another test.
It is safer to create a new one every time, while the performance hit is
negligible.
Change-Id: I404d240b29dddffb07899e7e529e7205282bd1d2
Signed-off-by: Simon Marchi <simon.marchi@polymtl.ca>
Unlike those in AsyncCompletionWaitor, these functions are based on
queries. The patch also changes occurences in MIMemoryTest where it
makes sense to use synchronous functions.
Change-Id: Id5e47b7634153d916bf896e47f6cc48f1a4727bd
Signed-off-by: Simon Marchi <simon.marchi@polymtl.ca>
Factor out the code for testSettingVariableWithSet and
testSettingVariableWithPrint.
testSettingVariableWithSetWithMemory is not exactly the same, so I
didn't factor it out.
Change-Id: Ib4e79eda4851ec2291fcf32054694b76e40c65ca
Signed-off-by: Simon Marchi <simon.marchi@polymtl.ca>
