[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
|
Re: [cdt-debug-dev] Using Eclipse for remote debugging
|
Mikhail Khodjaiants wrote:
----- Original Message -----
From: "Joel Brenner" <jogava@xxxxxxxxxxx>
To: <cdt-debug-dev@xxxxxxxxxxx>
Sent: Thursday, April 17, 2003 2:43 PM
Subject: Re: [cdt-debug-dev] Using Eclipse for remote debugging
Alain Magloire wrote:
Maybe I've posed the wrong question.
I'm now running sparc-elf-gdb connected via the extended-remote
protocol to
my
personal debug-server (located on the same host machine). The debug
server is
connected via a serial cable to a hardware debug unit that I've on a
remote
sparc processor. On top of that I usually I run ddd.
My question is : can Eclipse take the control over gdb like ddd does?
PS:
in the DebuggerTab I've only GDB as option.
Sorry for the stupid questions but I'm new on Eclipse and GSB
interfaces.
- Eclipse will do the same as ddd(I think, not knowing ddd), it will
connect to
the host:port or serial that the gdbserver is running. This mean that
somehow you
will have started gdbserver on the target and uploaded the application
on the target.
I can't run gdbserver, I've to run my own debug-server usually on the same
machine
than gdb (not on the target in any case). Then I start sparc-elf-gdb with
target
extended-remote host:xxxx. This allows gdb to download and run a program
to the
target usign the my debug-server.
Am I right to suppose that Eclipse talks directely to gdb and the
communication
channel between gtb and my debug-server is don't care ?
If so I've probably only to switch on "-gdb-set auto-solib-add on" in
gdb. (I can
verify it only tomorrow in the office).
Last two questions:
- what is the GDB/MI protocol ?
This is an excerpt from gdb documentation:
"gdb/mi is a line based machine oriented text interface to GDB. It is
specifically intended to support the development of systems which use the
debugger as just one small component of a larger system."
- does Eclipse starts gdb when a debug session is started or have I to
start it
outside and Eclipse simple try to take the control over it ?
When you launch a debug session CDT starts gdb automatically and passes to
it the information defined in the launch configuration.
Thanks Joel
- The "GDBServer" debugger launch tab to do this(setting serial or host)
is in the
head branch not your snapshot, it is code donated by MontaVista.
- The "auto" error usually comes when Eclipse debug session starts
it tries to do in the GDB/MI protocol:
(gdb) -gdb-set auto-solib-add on
as the first step. Try on your sparc-elf-gdb command line
(gdb) set auto-solib-add on
see if it returns an error. Because even if the "GDBServer" Tab is not
in your
snapshot you can still pass some commands in a ".gdbinit" file.
_______________________________________________
cdt-debug-dev mailing list
cdt-debug-dev@xxxxxxxxxxx
http://dev.eclipse.org/mailman/listinfo/cdt-debug-dev
_______________________________________________
cdt-debug-dev mailing list
cdt-debug-dev@xxxxxxxxxxx
http://dev.eclipse.org/mailman/listinfo/cdt-debug-dev
_______________________________________________
cdt-debug-dev mailing list
cdt-debug-dev@xxxxxxxxxxx
http://dev.eclipse.org/mailman/listinfo/cdt-debug-dev
What I see is that I don't have shared library debug support on my sparc-elf-gdb
(which makes sense for an embedded target). (It don't accept "set auto-solib-add
on") but Eclipse try to enable it. Is there a vay
to tell to Eclipse that it should not enable shared library support when
it starts gdb (don't ask for auto-solib-add on )?
--
Joel Brenner -- Designer
E-mail: joel.brenner@xxxxxxxxxxx
Phone: +41 91 612 46 00 -- Fax : +41 91 612 47 01
Direct: +41 91 612 47 12
www.nemerix.com
NemeriX SA Stabile Gerre 2000
PO Box 425 6928 Manno, Switzerland
----------
