Skip to main content
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [cdt-dev] GDB Console view
It should not be like that.  The console is independant from the Debug view.
Could it be that your console got replaced by another before you noticed the
output?

From: cdt-dev-bounces@xxxxxxxxxxx [mailto:cdt-dev-bounces@xxxxxxxxxxx] On Behalf Of Sergey Prigogin
Sent: Wednesday, December 14, 2011 11:57 AM
To: CDT General developers list.
Subject: Re: [cdt-dev] GDB Console view



On Wed, Dec 14, 2011 at 8:29 AM, Marc Khouzam <marc.khouzam@xxxxxxxxxxxx> wrote:
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.

I did select the right console from the list before entering gdb commands, but it didn't work when the 'gdb' node was not selected.

-sergey
 
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

 

From: cdt-dev-bounces@xxxxxxxxxxx [mailto:cdt-dev-bounces@xxxxxxxxxxx] On Behalf Of Sergey Prigogin
Sent: Wednesday, December 14, 2011 2:43 AM
To: CDT General developers list.
Subject: Re: [cdt-dev] GDB Console view

 

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:

Is the target suspended?


On 13.12.2011, at 21:07, "Marc Khouzam" <marc.khouzam@xxxxxxxxxxxx> 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.

 

-sergey


_______________________________________________
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


_______________________________________________
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


Back to the top