This is the mail archive of the
gdb@sources.redhat.com
mailing list for the GDB project.
RE: Debugging the STUB.
- From: "Atul Talesara" <atul dot talesara at nevisnetworks dot com>
- To: <gdb at sources dot redhat dot com>
- Date: Fri, 13 Feb 2004 20:42:10 +0530
- Subject: RE: Debugging the STUB.
Thanks Andrew. But, being quite new to GDB WORLD, would
anyone mind briefing me on the set up with 'simulator'?
JTAGS isn't feasible for me. I didn't find info thro' google'ing :-(
Thanks and Regards,
Atul P Talesara
Nevis Networks Inc.
Pune IT Park
Bhau Patil Marg,
34 Aundh Road
Pune 411003, India
http://www.nevisnetworks.com
------------------------------------------------------------------
In science knowledge comes first and then faith follows.
In spirituality faith comes first and then knowledge follows.
-Sri Sri
------------------------------------------------------------------
-----Original Message-----
From: Andrew Cagney [mailto:cagney@gnu.org]
Sent: Friday, February 13, 2004 8:27 PM
To: Atul Talesara
Cc: gdb@sources.redhat.com
Subject: Re: Debugging the STUB.
> Hello Everybody,
> This might sound as a very naive question.
> I'm using GDB for remote debugging and I have applied the
> "kgdb" patch to the target. Now, is there a way of debugging
> the "kgdb" patch itself? In essence, is there a straightforward
> way to debug the "remote stub" itself?
Either a JTAG like device, or a simulator come to mind. Failing that,
printf to a separate serial interface.
Andrew