I mean this:
[New Thread 8416.0x2130]
n
n
22 cout << "!!!Hello World!!!" << endl; // prints !!!Hello World!!!
Having it echo back the second ‘n’ looks dumb. Also hitting the enter key doesn’t repeat the last command like it does in gdb, it does nothing. That leads you
to lose faith that it’s going to do what you want.
We should be running interactive consoles in a terminal view-like environment (or the terminal view itself if it can be repurposed that way.)
From: cdt-dev-bounces@xxxxxxxxxxx [mailto:cdt-dev-bounces@xxxxxxxxxxx]
On Behalf Of Marc Khouzam
Sent: Wednesday, December 14, 2011 11:29 AM
To: 'CDT General developers list.'
Subject: Re: [cdt-dev] GDB Console view
You don't actually need to select the gdb node in the debug view. That is just a way to
easily make the gdb console jump to the front. You can select the gdb console from
the console view and then pin it, so that it does not get replaced by another console.
About the echoing to the console, what do you mean?
From:
cdt-dev-bounces@xxxxxxxxxxx
[mailto:cdt-dev-bounces@xxxxxxxxxxx] On Behalf Of Schaefer, Doug
Sent: Wednesday, December 14, 2011 11:20 AM
To: CDT General developers list.
Subject: Re: [cdt-dev] GDB Console view
Definitely a usability issue. Playing with it yesterday I also notice it’s a bit weird in how it echoes to the console. I wonder if it needs its own view, something
like the terminal view. Anyone else have thoughts?
:D
The thing I was missing is selection of the 'gdb' node. Everything is working when this node is selected.
-sergey
On Tue, Dec 13, 2011 at 10:08 PM, Elmenthaler, Jens <jens.elmenthaler@xxxxxxxxxx> wrote:
I just tried it with master and it works (on Linux).
Launch a debug session, select the 'gdb' node in the
debug view, then type n (next) on the console.
You should see the code step to the next line.
No?
From:
cdt-dev-bounces@xxxxxxxxxxx [mailto:cdt-dev-bounces@xxxxxxxxxxx]
On Behalf Of Sergey Prigogin
Sent: Tuesday, December 13, 2011 3:04 PM
To: CDT General developers list.
Subject: Re: [cdt-dev] GDB Console view
On Tue, Dec 13, 2011 at 11:58 AM, Marc Khouzam <marc.khouzam@xxxxxxxxxxxx> wrote:
Make sure you select the 'gdb' console and not the 'gdb traces' console.
The 'gdb traces' console is only printing the communication with GDB
but does not accept input. Well, it does accept input but it does nothing
with it. The idea was simply to allow the user to add empty lines
or some comments directly in the trace, but nothing else.
I was trying with gdb console, not with gdb traces :-(
From:
cdt-dev-bounces@xxxxxxxxxxx [mailto:cdt-dev-bounces@xxxxxxxxxxx]
On Behalf Of Sergey Prigogin
Sent: Tuesday, December 13, 2011 2:54 PM
To: CDT General developers list.
Subject: [cdt-dev] GDB Console view
Can GDB console view be used for manually entering GDB commands? It seems to accept anything I type, but doesn't seem to send that to GDB.
_______________________________________________
cdt-dev mailing list
cdt-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/cdt-dev
_______________________________________________
cdt-dev mailing list
cdt-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/cdt-dev
|