[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
Re: [cdt-dev] GDB Console view
|
Maybe it is what Jens mentioned? Your target was
running so GDB could not answer (all-stop mode only)?
After typing to the gdb console, go to the gdb traces
console and see if your command was sent
to gdb. For example, if I type 'show version', in the
gdb console, I see the following in the gdb traces:
528,189 35-interpreter-exec console "show
version"
On Wed, Dec 14, 2011 at 9:03 AM, Marc Khouzam
<marc.khouzam@xxxxxxxxxxxx>
wrote:
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?
The commands that I typed were still there.
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?
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
_______________________________________________
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