Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.

Bug 370423

Summary:	[remote] Bring RemoteShell console to the front when user selects process/thread/stack in debug view
Product:	[Tools] CDT	Reporter:	Marc Khouzam <marc.khouzam>
Component:	cdt-debug-dsf-gdb	Assignee:	Project Inbox <cdt-debug-dsf-gdb-inbox>
Status:	NEW ---	QA Contact:	Jonah Graham <jonah>
Severity:	enhancement
Priority:	P3	CC:	anna.dushistova, cdtdoug, pawel.1.piech
Version:	8.1.0
Target Milestone:	---
Hardware:	PC
OS:	Linux
Whiteboard:

Description Marc Khouzam

2012-02-02 06:28:30 EST

Bug 370376 removed the useless inferior console for a remote non-attach launch.  Now, when the user selects the process in the Debug view, it is the GDB console that is brought to the front.  This is better than before, since the useless inferior console was being brought to the front.

For a manual remote session, I think we are doing what we should by bringing the GDB console to the front.

For an automatic remote session though, it would be nicer to bring the Remote Shell session to the front, since it is actually dealing with the inferior IO.

Comment 1 Anna Dushistova

2012-02-02 10:45:42 EST

Right now it switches to the remote shell console for the output, and in the beginning before gdb is launched. Do you think this is insufficient?

Comment 2 Marc Khouzam

2012-02-02 11:13:43 EST

(In reply to comment #1)
> Right now it switches to the remote shell console for the output, and in the
> beginning before gdb is launched. Do you think this is insufficient?

Notice that if you select 'gdb' in the debug view, the 'gdb console' automatically comes to the front, when you select 'Remote Shell', its console comes to the front.  But when you select the launch node, it is the gdb console that comes to the front; and if you select a process or thread or stack frame, the console does not change (even if it is the gdb console showing).

To see this, select the gdb console, then select a stack frame.  The console showing remains the one for gdb.

To be consistent with the other launches, we would need to show the Remote Shell console when pressing on the Launch or the process/thread/stack nodes.

The code to change is in DSF-GDB: ConsolePageParticipant.getCurrentProcess().  When coding this I made the assumption that the only process of the launch was the gdb process.  This is wrong for the automated remote launch.