This allows us to consider more than just the os and arch in the build
config names as required by the selected toolchain.
Change-Id: I3e1a52c756aca13fbe6c83a95f9a86bb2f286f1d
Adding unit test for MIAsyncErrorProcessor. The test adds breakpoint on
0x0 address and try to continue and step return. It asserts that the
target is in stopped state and error as reason in both cases. Then it
removes all the breakpoints and resumes the target and asserts that
target is in resumed state.
Change-Id: I2e024e0d5f55b4e9464a6f2b7a2b0c78bee4e8e8
Signed-off-by: Umair Sair <umair_sair@hotmail.com>
Command abort can occur for commands that are run not just in context of
thread, instead stack frame is also present, e.g., step return in case
of this bug. Updated the implementation to get IExecutionDMContext from
the command context if it is not IExecutionDMContext itself.
Change-Id: Ia6cccffba8bde28e22eca46211747de31084f25a
Signed-off-by: Umair Sair <umair_sair@hotmail.com>
If we call it without cloning, we associate the value with every place
that has a reference to that CPPBasicType object, which could involve
completely unrelated entities.
Change-Id: Icff6c32d15ee6dbc55e363b2de9a166e03440f74
This started happening when I added the ErrorBuildConfiguration which
returns a null id. This happens when you create a CMake project and
add a new launch target. Not totally sure how we got an error config
for that. Will investigate that later.
Change-Id: I1a4e7c528d2cee101a432d386ad6a7505b9983b6
Although a little profile "magic" is needed, by adding -DuseSimrelRepo
to the command line to enable and disable the correct profiles
individual mvn projects can be built against the simrelRepo.
This enables, for example, the ability to build the standalone debugger
against the simrel repo without having to change how normal builds are
done by using:
mvn verify -DuseSimrelRepo -f debug/org.eclipse.cdt.debug.application.product
A simrel p2 site can also be provided with -Dsimrel-site=<url>
Change-Id: I45a636c3c1042bc2fbb6eea5129c6553027e92df
When at the same time never join wrapped lines and next line
for opening function brace were selected, two tabs were added.
Change-Id: I90f606bf7f8b7bb7e83f3ae85d7cbb9cd0146b97
Signed-off-by: Marco Stornelli <marco.stornelli@gmail.com>
Use the toolchain type and id as the key to the Map holding the
toolchain files instead of the Path to the file. Also simplifies the
build config since we can always figure out the toolchain file from
the toolchain. Deprecate getting toolchain by path since that shouldn't
be needed any more.
Also took the opportunity to add javadoc to the interfaces.
Change-Id: I11ae2ad8177a3f60399742c8c19576f85ea4b8c0
Because of the missing getRecordSize implementations, subclasses would
starting writing in records that were thought to be malloc'ed by
the parent but it was instead writing in other blocks, possible used
by other PDOM objects or free blocks to be used later and now not initialized
to 0.
This could lead to a few different exceptions like
- BufferUnderflowException(Chunk.getChars)
- CoreException: Corrupted database
- ArrayIndexOutOfBoundsException(AbstractIndexerTask$IndexFileContent.merge)
and possibly others.
Change-Id: Ie6d1986a22a9fb5f5e90cb741046d098ebf10a90
Signed-off-by: Marc-Andre Laperle <malaperle@gmail.com>
README:
Create a C/C++ Application launch as normal, and in the Launch
Configuration dialog click "Select other..." at the bottom/center
and selecting GDB (DAP) Debug Process Launcher
(you can't do this in the LaunchBar's dialog as it does not support
changing the launcher).
Then debug as you normally do (with less features so far :-)
Change-Id: Ia36acedf064b3774c6ac2a863880eaf7efe9c399
When DSF was first created it was a separate project that borrowed
heavily from CDT, as such (AFAICT) some code was copied from
o.e.cdt.launch to DSF. This commit de-duplicates some of that code
as the DAP implementation wants to reuse the code too and another
copy is not wanted.
Change-Id: Ie54187dabc9c32224575c0bf51bcabfab00ca340
