- hover with ctrl+mouse underlines word under cursor
- ctrl-click tries to open the word:
- if a relative path (not starting with /) a full path is
obtained by prepending the shell cwd
- if the fullpath maps to a workspace file, it is opened
- otherwise open the OpenResource dialog with the word as
filter text
- if there is line/column information (separated by colons)
then the opened editor jumps to that line
- http and https words are opened in a browser window
Change-Id: I3f46accbf1eac6743d7b0c3b34bf30ac5e7523bb
Signed-off-by: Fabrizio Iannetti <fabrizio.iannetti@gmail.com>
Also-by: Jonah Graham <jonah@kichwacoders.com>
Signed-off-by: Jonah Graham <jonah@kichwacoders.com>
Note that:
- doc/org.eclipse.cdt.doc.isv
- doc/org.eclipse.cdt.doc.user
were updated in commit 149aca51f9 made
this release cycle.
Change-Id: I5b19c7ba14d1c3f837163c109603f9a330e9f138
In some situations, it makes sense to have a build structure parallel
with the source tree, and it this case, the build results may not be
part of the resources visible in the Eclipse workspace.
Current implementation allows absolute paths to the binary to debug.
While it works, it's a cumbersome way to handle the above situation.
By resolving the relative path outside of Eclipse scope allows to point
to files that are not part of the Eclipse workspace, allthough the path
is relative to a project in the workspace.
Contributed by STMicroelectronics
Change-Id: I284a5dad61e692dae4029e5f142d23d8cda98ed0
Signed-off-by: Torbjörn Svensson <torbjorn.svensson@st.com>
The ThrowNew JNI method requires the message to be encoded in
"modified UTF-8". The FormatMessage WinAPI method can return a string
using any encoding, so it needs to be converted to UTF-8 in order
to have it visible in the exception message.
To further help, try to extract the message in English and fall back
to the Windows installation language as a last resort.
Prefix the error message with the error code from the GetLastError()
function.
Contributed by STMicroelectronics
Change-Id: Id76ffd83e2d3ad1f061780c7ee0892c9b378649b
Signed-off-by: Torbjörn SVENSSON <torbjorn.svensson@st.com>
this fixes cases where a single test failing does not clean up
properly causing subsequent tests to then fail.
Change-Id: I4bd9c08e5ce1a4cd2ccd5e710a446e6e96c4d353
Instead make the tests non-intermittent. If tests are flaky, they
should be moved to JUnit5 and marked with the flaky tag.
Change-Id: I9c165ec8f16c65383d93d64d17047c0a2597b81c
Many of the disabled tests were failing because they were dependent
on specific combinations of GDB + GCC and where exactly code
stops and steps effect when entering functions. The old code
mostly ran to a function and then stepped a known number of times.
But what changes between GDB versions is how many steps are needed.
Therefore for all failing tests update to run to a specific line
number by using tags in the .cc file and running to them to make
sure the test is precisely on that line.
This partially reverts commit 8220215a2e
and 92272c6465
Reason for revert: These tests were "temporarily" disabled a while ago
as part of the JIRO migration in Bug 545624.
Change-Id: I703429c8a81c856360f1cb4e899026200527f7c6
MIExpressionsTest.testNestedBaseChildrenBug accesses this field like
this -data-evaluate-expression "*((((*(class Base*) this)).pNested))"
which, as pNested isn't init, can cause a Cannot access memory at
address 0x0 error.
Change-Id: Ie6ba01be3499df6e72e714bc5c02dcd5355468bf
The test for ThreadStackFrameSyncTest accessed some state in the
IGDBFocusSynchronizer from outside the Executor thread.
The test also was not waiting on events to synchronize with
the executor thread, instead using Thread.sleep().
There was also some unneeded code due to not using the ServiceEventWaitor
in all places it could be used.
This was leading to race conditions and flaky test failures.
Change-Id: Ib6a3273e20f4383714edc491de9dd9330b250487
Java 16 restricts some reflection. The serializing of scannerInfoCache
with gson does some reflection on Pattern which isn't allowed.
Fortunately the reflection is not needed, we just have to prevent
gson from calling setAccessible by providing our own serialization
for the IExtendedScannerInfo
Change-Id: I0db5cec9cfec1ac4caabd2e67f1d6a336e361023
System.arraycopy is more error prone and subsequent commits will
be modifying the array. This commit is to keep unrelated code
separate.
Change-Id: I2490318176da3e631a63974ffe5fa62da44a96ea
Upgrade the tests to JUnit5 so they can be marked as flaky and slow.
Also removed a bunch of unused code.
This partially reverts commit 8220215a2e.
Reason for revert: These tests were "temporarily" disabled a while ago
as part of the JIRO migration in Bug 545624.
Change-Id: I111cf4d9d9f5e07e49074ca2355a3d1f52fb1070
These launch files are basically all defaults and fill every devs space
but no one is running them on a regular basis.
Change-Id: I194dadd2ca55a20489935e690e3cd94357026389
Using the Consumer interface means that code navigation is substantially
harder. e.g. open ImportMemoryDialog and do a call hierarchy on who
calls scrollRenderings.
You end up in Consumer.accept, which (naturally) has 100s of callers, so
identifying which ones are relevant is very difficult.
Change-Id: I8817568e992955d5b01a591a9cffb2447b9e5008
This comes up when doing headless DSF-GDB tests, not sure users can
hit it, but rather than logging an NPE, just check for it upfront.
Change-Id: I224b7e3a881c5e7bc2e1c1b00c1c3da58c745567
In some targets (such as the build machines @ Eclipse) gdb is
returning thread names for remote debugging. No longer fail tests
in this case as long as the provided name is empty or correct.
Change-Id: I5f59f279a9d477e2c1ccb32098bbe1dad08cf334
rebuilt docker images have small binary differences
in the jnilibs due to a rebuilt macOS toolchain being
used.
Change-Id: I25dc951e1e8c7c94a799d63a4c0db644d1f1be1e
Added missed license headers
Updated baseline for the parent pom to CDT 10.2
Updated version for pom.xml to 10.3
Updated version for features and bundles to CDT 10.3
Updated copyright for about.properties to be 2021
Incremented version + 100 where needed
Change-Id: I79666fcc0402fee6607499d7dce1eaf87a5f446d
Signed-off-by: Alexander Fedorov <alexander.fedorov@arsysop.ru>
Increment version for org.eclipse.cdt.doc.user
Change-Id: I893d0c91874624d579e0069bc656cf702c84d8c7
Signed-off-by: Alexander Fedorov <alexander.fedorov@arsysop.ru>
Increment version for org.eclipse.cdt.doc.isv
Change-Id: Iaecdce9bad474af7583329ce9566dc4a047bf641
Signed-off-by: Alexander Fedorov <alexander.fedorov@arsysop.ru>
Increment version for org.eclipse.cdt.debug.gdbjtag
Change-Id: Ib2cc5067f4c87dac27e44e5ee17535e127579f24
Signed-off-by: Alexander Fedorov <alexander.fedorov@arsysop.ru>
Updated baseline to 2021-03 for
* cdt-baseline.target
* CDT.setup
* parent pom is not changed
Updated target to 2021-03 where it was pointing to older versions for
* cdt.target
* CDT.setup
Change-Id: Ie8117b4cb6f86c8ad105710d14dde6222380d289
Signed-off-by: Alexander Fedorov <alexander.fedorov@arsysop.ru>
All the hard work had been done before, simply no one had actually
added the bit of code to update the title based on the listener.
Change-Id: Icdbc7b9b0a9b8fccf7d4eddf8d20674e50e0a170
When invoking the headless build, the verdict should be the "sum" of
all the build configurations. If one build configuration fails, then
the verdict of the build should also be "failed".
Contributed by STMicroelectronics
Change-Id: Ic3237d3531657f7f89c9338142ebf8fdb477c481
Signed-off-by: Torbjörn SVENSSON <torbjorn.svensson@st.com>
Moved handling of "-help" to a new plugin using the same approach as
was used for the JavaCodeFormatter in bug 543363. This mainly allows
to get the help text even if the workspace is missing.
Contributed by STMicroelectronics
Change-Id: I4ee2e93f0e8fed13ddebd70c3bce58f047aa1d12
Also-by: Jonah Graham <jonah@kichwacoders.com>
Signed-off-by: Torbjörn SVENSSON <torbjorn.svensson@st.com>
