This is the mail archive of the
gdb@sources.redhat.com
mailing list for the GDB project.
Re: GDB interface with simulator
- From: Rama Singh <rama10nov at yahoo dot co dot in>
- To: Daniel Jacobowitz <drow at mvista dot com>, Doug Evans <dje at transmeta dot com>
- Cc: gdb at sources dot redhat dot com
- Date: Thu, 20 Nov 2003 10:02:03 -0800 (PST)
- Subject: Re: GDB interface with simulator
Hi,
Thanks for the answers. I have certain newbiew
querries for gdb-stubs.
I do not hve any OS running on my target board and
hence there is no point in porting of gdbserver. I
need to write the gdb-stub for my architecture.
Now there is a conept of threads which may share data
and insns. Going though some of the discussions
previously about thread support in gdb, i realise that
gdb does support threads. Have some querries regarding
this.
Is it possible, under a gdb-stub implementation, that
once a thread has hit breakpoint and all the others
are stop, we can selectevely resume some of the
threads and step on the rest?
Also looking into gdb-stub implementation, I have
found that there is no way of specifying the thread
id? a search on the net provided a protocol document
as
http://world.std.com/~qqi/download/protocol.txt
Is this a document for the gdb remote protocol for
stubs?
I do not see any support for seting and removing
breakpoints in sparc-stub.c. Does that mean that for
setting breakpoint, we need to put in breakpoint() and
recompile the whole application again?
How do I specify gdb to which thread it has to hook
to?
I do a 'target remote COMM' How to read specific info
about a thread?
Just to make things simple, where can I find a
gdb-stub implementation for MIPS architecture.
Thanks and Regards
Rama Singh
--- Daniel Jacobowitz <drow@mvista.com> wrote:
> On Fri, Nov 14, 2003 at 09:07:17AM -0800, Doug Evans
> wrote:
> > =?iso-8859-1?q?Rama=20Singh?= writes:
> > > I wish to use my simulator as an
> > > independent process running on the same machine
> or on
> > > other machine.
> >
> > Old versions of gdb had a file in gdb/gdbserver
> called low-sim.c.
> > IIRC, one would use this file in gdbserver and
> would link gdbserver
> > with libsim.a. You would then run this program on
> the host
> > you want to run your simulator on and use "target
> remote <simhost>:<port>"
> > in gdb to talk to gdbserver+sim.
> >
> > Maybe you could grab that file from an old version
> of gdb (e.g. 5.3)
> > and try to make it work with the version of gdb
> you have.
> > [or maybe even just build gdbserver from 5.3
> sources]
> >
> > I don't recall why support for gdbserver+sim has
> been removed.
> > Maybe I'm mistaken and it's still there and I just
> can't see it.
>
> Because there was no point. The current simulators
> link directly into
> GDB, and the simulator interface has changed since
> anyone tried to use
> gdbserver that way. The correct thing is to write a
> layer in your
> simulator that serves the same purpose (speaks the
> remote protocol).
> It's not too hard.
>
> --
> Daniel Jacobowitz
> MontaVista Software Debian
> GNU/Linux Developer
__________________________________
Do you Yahoo!?
Free Pop-Up Blocker - Get it now
http://companion.yahoo.com/