linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: "Mark Chambers" <markc@mail.com>
To: "Steve Iribarne \(GMail\)" <netstv@gmail.com>
Cc: linuxppc-embedded@ozlabs.org
Subject: Re: kernel debugging
Date: Thu, 4 May 2006 16:13:42 -0400	[thread overview]
Message-ID: <016d01c66fb7$3e815740$6601a8c0@CHUCK2> (raw)
In-Reply-To: b4b98b690605041251s40f88731i1edfdfb324da38b4@mail.gmail.com

>> >
>> > This is more a general question to see what others do out here.  I am
>> > begining to get sick of printk debugging.  I work on two different PPC
>> > boards.  An 860 and 8260.
>> >
>> > I want to get some feedback on the best kernel debugger to use.  I
>> > have been looking at three.
>> >
>> > 1.  kgdb
>> > 2.  kdb
>> > 3.  UML
>> >

For the 860 you can purchase a hardware debugger from www.denx.de for
50 Euros.  For the 8260 you must buy the more expensive BDI2000, but
that is Freescale's fault.  But the look and feel of BDI2000 is the same as
BDI4GDB, just faster, so you can decide whether it's worth the money for 
you.
When you say 'kgdb' you imply 'gdb' which is the standard GNU-world
debugger.  kgdb is a means for letting a kernel communicate with a PC based
(or equivalent) gdb and is an alternative to a hardware debugger.  Also,
check out ddd, a front end for gdb.

IMHO, these serial debugging ports on PPC are the greatest thing since 
sliced
bread and it would be foolish not to take advantage of them.

Mark C. 

  reply	other threads:[~2006-05-04 20:13 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-05-03 14:11 kernel debugging Steve Iribarne (GMail)
2006-05-03 16:06 ` David Hawkins
2006-05-04  9:20 ` David H. Lynch Jr.
2006-05-04 19:51   ` Steve Iribarne (GMail)
2006-05-04 20:13     ` Mark Chambers [this message]
     [not found] <406B9D084FAFD4118C980008C79FADB901B57FF9@ALBMAIL>
2003-04-15 15:38 ` Kernel Debugging Wolfgang Denk
  -- strict thread matches above, loose matches on Subject: below --
2003-04-14 21:38 Yang, Bo
2003-04-14 23:18 ` Wolfgang Denk

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='016d01c66fb7$3e815740$6601a8c0@CHUCK2' \
    --to=markc@mail.com \
    --cc=linuxppc-embedded@ozlabs.org \
    --cc=netstv@gmail.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;
as well as URLs for NNTP newsgroup(s).