From: "Steve Iribarne (GMail)" <netstv@gmail.com>
To: linuxppc-embedded@ozlabs.org
Subject: kernel debugging
Date: Wed, 3 May 2006 07:11:48 -0700 [thread overview]
Message-ID: <b4b98b690605030711q69426a59j28db8e38be73f1f0@mail.gmail.com> (raw)
Hello.
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
I am leaning towards kgdb, but before I jump in I thought I'd put this
out to the best group I could think of linuxppc. Because I am sure
most of you are using something! :)
Thanks.
-stv
next reply other threads:[~2006-05-03 14:17 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-05-03 14:11 Steve Iribarne (GMail) [this message]
2006-05-03 16:06 ` kernel debugging 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
[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=b4b98b690605030711q69426a59j28db8e38be73f1f0@mail.gmail.com \
--to=netstv@gmail.com \
--cc=linuxppc-embedded@ozlabs.org \
/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).