Cleaned up some error messages. Especially when a system has no
serial ports. Also added a delay when ports are closed since some
serial port drivers (FDTI in particular) take a bit longer to
properly close. Especially important in pause situations where we
want to use the serial port for some other purpose right away.
Change-Id: Ifc9b7171682962e0aed8e9ed9ebf5472fc9e8206
Until we can figure out a nice fix for it. See bug for the findings
so far. Hopefully this will just be a stopgap.
Change-Id: Id4f7d91645fd25b140d3eb256da5ebdedc1d0e3f
Signed-off-by: Marc-Andre Laperle <marc-andre.laperle@ericsson.com>
(cherry picked from commit 6adc3c29a6)
This is mostly to mitigate the effects of a bug in ProjectionViewer
(bug 509559). See the discussion in bug 507138 for details.
Change-Id: Icf36b54d6a11892f02214a168ef1c9c284478710
We previously guarded against recursion in this case, but the
result was an invalid composite value that could cause problems
down the line.
This patch avoids getting into the recursion to begin with by
skipping the processing of static fields in a case where it's
not necessary to begin with.
Change-Id: Ic3a346092bb7ad5c94cd15871110dd17ecd64886
- Avoid a ClassCastException in CPPConstructor.getMemberEvaluation()
- Fix an unsafe method call in EvalCompositeAccess.getType()
- Emit a log message in an error case in ASTInternal.getDefinitionOfBinding()
- Emit a log message in an error case in CompositeValue.setSubValue()
Change-Id: I5932c8b661e31eff32c2bb138efdb3029894d0ab
This catches recursion along paths in EvalUtil.getVariableValue() that don't
go through CPPVariabble.getInitialValue().
The patch also improves caching in EvalInitList.
Change-Id: I343bbf1bb7493b2c83771de3659209e5d512fd80
The CDT does not need to depend on itself.
I believe this dependency was added while troubleshooting another
problem.
Change-Id: Ic79cc8c00c67f323198bb49d1596e4d254bbd924
The GdbFullCliConsole has id: GdbFullCliConsole.#ContextMenu
The GdbBasicCliConsole has id: GdbBasicCliConsole.#ContextMenu
The commit also adds an example of adding a new button to those menus in
org.eclipse.examples.dsf.gdb
Change-Id: If9579e3e60524f39a332df868f512c5f457043ed
Due to a GDB bug present in numerous versions of GDB
https://sourceware.org/bugzilla/show_bug.cgi?id=19637
CDT can fail to display advanced memory info and
registers view properly.
This fix is more lenient, and if the user really wants
to see the registers, a workaround for GDB's bug is linked
to.
Change-Id: Ia78947e29a1e446837ef992d470dfd14f047bda2
Commit 6335a5c2ba reverted
a previous commit which made the changes being reverted
here unecessary.
This reverts commit 896eba55c5.
Change-Id: I890a67513b35df7708f9fc33c0be3e879fdb9e0e
Includes splitting out and expanding CommandLineArgsTest
from LaunchConfigurationAndRestartTest.
Change-Id: I19fa97a847d908c1c780ca767cf688f26a51d684
Signed-off-by: Jonah Graham <jonah@kichwacoders.com>
In all-stop mode for a remote session, it's not possible to have the
target switch thread, while the target is running. At the moment, the
GDB focus synchronizer attempts to switch the thread in that case, when
the user switches thread in the Debug View, which can fail and ends-up
logging an error.
This patch silences this error.
Change-Id: Ib21347fe9f4c31b3a42b4a83d289dbcd10b74a07
The previous all-stop implementation use Ctrl-C (variants) to suspend
the target program. This option is not supported when using the new
GDB full CLI console provided in GDB 7.12.
So the alternative is to send the mi command -exec-interrupt to suspend
the target, however this option requires the use of target async-on mode
(already in use for non stop mode).
This update makes all-stop mode use target async mode when using
versions higher or equal to GDB 7.12.
This update also removes the non-stop mode restriction initially
implemented for the use of the new GDB Full CLI console.
Change-Id: Iabef20bdee814d413fc338f9ec8c2d99d6311c20
This commit introduces a PersistentPTY. By using it, we now allow the
user to restart the process from the GDB console (by pressing 'run').
In this case, the I/O will continue using the PersistentPTY.
Previously, the PTY would have been closed, and GDB would fail to
restart the process because it would fail to use the closed PTY.
Change-Id: I395b402e297a2043af8fce33df163eddef9e6c7a
This patch synchronizes the GDB focus when the user selects a process
node in the DV.
When the user selects a new process (inferior) from the GDB console, we
are already synchronizing the DV to the thread/frame that GDB selects
from that process.
Change-Id: I11dfd175d51ec49e969f4d07288f80f7ea72a3e1
