From: Jun Sun <jsun@mvista.com>
To: Daniel Jacobowitz <dan@debian.org>
Cc: Geoffrey Espin <espin@idiom.com>,
"Siders, Keith" <keith_siders@toshibatv.com>,
"Linux-Mips (E-mail)" <linux-mips@oss.sgi.com>
Subject: Re: Debugging of embedded target applications
Date: Wed, 08 May 2002 11:16:22 -0700 [thread overview]
Message-ID: <3CD96B76.5090506@mvista.com> (raw)
In-Reply-To: 20020508023236.GA31840@nevyn.them.org
Daniel Jacobowitz wrote:
> On Tue, May 07, 2002 at 07:25:23PM -0700, Geoffrey Espin wrote:
>
>>On Tue, May 07, 2002 at 09:43:14PM -0400, Daniel Jacobowitz wrote:
>>
>>>>Does work it for kernel type debugging over *Ethernet*?
>>>>I see some docs saying "TCP/IP" connection... but does that
>>>>mean a special kind of network driver? Or a gdbstub/agent
>>>>outside the kernel in a special monitor?
>>>>
>>>What do you mean by kernel type debugging? It's not a kernel stub. It
>>>can debug user programs over TCP/IP or a serial line.
>>>
>>In traditional embedded RTOS land, "system-level debugging".
>>In the olden days one had to have BDM/JTAG hardware assist
>>to step thru truly arbitary bits of code, like interrupt handlers,
>>scheduler.
>>
>>The original question was about using using a hardware debugger.
>>Clearly using gdb/gdbserver is for apps only, AFAIK. Does one
>>bother with a h/w debugger for apps? Using kgdb with some kind
>>
>
> Actually, yes, you can. I believe at least the Abatron BDI can do
> this. Could be wrong, though.
>
I have used kgdb over JTAG.
Jun
next prev parent reply other threads:[~2002-05-08 18:17 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-05-07 22:05 Debugging of embedded target applications Siders, Keith
2002-05-07 22:15 ` Daniel Jacobowitz
2002-05-07 22:44 ` Geoffrey Espin
2002-05-08 1:43 ` Daniel Jacobowitz
2002-05-08 2:25 ` Geoffrey Espin
2002-05-08 2:32 ` Daniel Jacobowitz
2002-05-08 18:16 ` Jun Sun [this message]
2002-05-07 22:33 ` Geoffrey Espin
-- strict thread matches above, loose matches on Subject: below --
2002-05-08 13:05 Siders, Keith
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=3CD96B76.5090506@mvista.com \
--to=jsun@mvista.com \
--cc=dan@debian.org \
--cc=espin@idiom.com \
--cc=keith_siders@toshibatv.com \
--cc=linux-mips@oss.sgi.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox