This is the mail archive of the gdb@sources.redhat.com mailing list for the GDB project.

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]
Other format:	[Raw text]

Re: Debugging the STUB.

From: Andrew Cagney <cagney at gnu dot org>
To: Atul Talesara <atul dot talesara at nevisnetworks dot com>
Cc: gdb at sources dot redhat dot com
Date: Fri, 13 Feb 2004 09:57:12 -0500
Subject: Re: Debugging the STUB.
References: <36993D449C7FA647BF43568E0793AB3E4B8550@nevis_pune_xchg.pune.nevisnetworks.com>

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

References:
- Debugging the STUB.
  - From: Atul Talesara

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]