Target definitions and Oomph setup can specify default arguments for launch
configurations. Enabling assertions is especially useful when doing development
in DSF components.
Change-Id: I9bf56515559804b966fd7d3be0cabb726ddf5c4e
Signed-off-by: Marc-Andre Laperle <marc-andre.laperle@ericsson.com>
This makes it easier to change arguments for all tests. As a side-effect,
all tests now enable assertion (-ea) and have the same max heap size, etc.
Change-Id: I0965d40ba3283efe7eacdf927f6c302ee0ab30f0
Signed-off-by: Marc-Andre Laperle <marc-andre.laperle@ericsson.com>
- added more comments and fixed copyright
- changed one the functions in cache class from private to public
- changed request for stack frames to request for stack depths in
getFrames fallback
- removed an extra private function which is not used anymore
Change-Id: I405e0ad61c6f9bf00bdccd041c0897f423f0b947
specializations
if a binding is a member of a ClassInstance (owner) we should not try to
find a corresponding class template (target).
Change-Id: Ic865161f137ecb2a300afd03761cc26ee758b38b
Signed-off-by: Michi <woskimi@yahoo.de>
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>
- Implemented cache for stack trace (replaces original stack depth
cache with a cache of frames and depth)
- This is mostly done to mitigate bugs in gdb but it will also help
speed up the debugger since the mi cache doesn't cache commands with
different limits and does not know that if we requested frames already
we don't need to ask about stack depth anymore
- In case of unrecoverable errors I will also return some constant
depth like 5, later the front end will ask to fill it up and in many
cases gdb will be happy to do that, even if it failed to report the
proper depth in the first place. We originally just returned 1 but it is
really not enough for most of the cases. This will result in potential
white gaps at the end of trace, but it is better then showing just the
first frame when we have errors
Change-Id: I24b42fd7ffea082e8064a9c5348fd95c5f7777be
Signed-off-by: Alena Laskavaia <elaskavaia.cdt@gmail.com>
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>
Building documentation can take several minutes and is often not necessary.
I suggest that we leave it on by default so that people building locally
still get a full, consistent build of CDT but that it should be possible to
skip it on demand.
My build time went from 4:14s to 1:45s (without running tests).
Change-Id: Ic7c4535f3faf82080534d39ccbe6f452d8b52317
Signed-off-by: Marc-Andre Laperle <marc-andre.laperle@ericsson.com>
