From: "David H. Lynch Jr." <dhlii@dlasys.net>
To: "Steve Iribarne (GMail)" <netstv@gmail.com>
Cc: linuxppc-embedded@ozlabs.org
Subject: Re: kernel debugging
Date: Thu, 04 May 2006 05:20:52 -0400 [thread overview]
Message-ID: <4459C774.8000300@dlasys.net> (raw)
In-Reply-To: <b4b98b690605030711q69426a59j28db8e38be73f1f0@mail.gmail.com>
Everyone has their own debugging style.
Engineers seem to like hardware debugging tools. I have used some
very fancy debugging hardware, but except for extremely rare instances
it is more work to get setup
and figure out what you are trying to do than inserting some
debugging and rebuilding.
My idea of debugging hardware is a port with an LED on it I can try
to blink.
I also only rarely use software debuggers.
Most of the time when things go off the rails the critical question
for me is Where did things go wrong. Once I know that usually the
problem is obvious and I do nto need dumps of variables or memory.
I also do development across numerous platforms, OS's and languages.
I need debugging tools and techniques that are broadly portable. A
hardware debugging tool might help with board bringup, but it would be
of little use
for web or perl programming. Investing time and capitol in highly
specialized tools or knowledge requires being narrowly focused to get a
worthwhile payback.
Regardless, I think debugging is a sort of religious preference. You
need to know who you are and what you need. Other peoples experience is
useful but should not be determinative.
Steve Iribarne (GMail) wrote:
> 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
> _______________________________________________
> Linuxppc-embedded mailing list
> Linuxppc-embedded@ozlabs.org
> https://ozlabs.org/mailman/listinfo/linuxppc-embedded
>
--
Dave Lynch DLA Systems
Software Development: Embedded Linux
717.627.3770 dhlii@dlasys.net http://www.dlasys.net
fax: 1.253.369.9244 Cell: 1.717.587.7774
Over 25 years' experience in platforms, languages, and technologies too numerous to list.
next prev parent reply other threads:[~2006-05-05 1:35 UTC|newest]
Thread overview: 19+ 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. [this message]
2006-05-04 19:51 ` Steve Iribarne (GMail)
2006-05-04 20:13 ` Mark Chambers
-- strict thread matches above, loose matches on Subject: below --
2020-02-19 6:19 Kernel debugging Pankaj Vinadrao Joshi
2020-02-22 0:15 ` Valdis Klētnieks
2013-08-06 10:25 Kernel Debugging Saket Sinha
2013-08-06 11:04 ` Chaitanya Gotkhindikar
2005-11-03 20:29 kernel debugging Siju George
2005-11-03 20:34 ` Kip Macy
2005-07-24 13:15 UmaMaheswari Devi
2005-07-24 14:02 ` Jesper Juhl
2005-07-24 14:03 ` Jesper Juhl
2005-07-25 19:23 ` uma
2005-07-25 20:02 ` Lee Revell
[not found] <406B9D084FAFD4118C980008C79FADB901B57FF9@ALBMAIL>
2003-04-15 15:38 ` Kernel Debugging Wolfgang Denk
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=4459C774.8000300@dlasys.net \
--to=dhlii@dlasys.net \
--cc=dhlii@comcast.net \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.