From: "Steve Iribarne (GMail)" <netstv@gmail.com>
To: dhlii@comcast.net
Cc: linuxppc-embedded@ozlabs.org
Subject: Re: kernel debugging
Date: Thu, 4 May 2006 12:51:26 -0700 [thread overview]
Message-ID: <b4b98b690605041251s40f88731i1edfdfb324da38b4@mail.gmail.com> (raw)
In-Reply-To: <4459C774.8000300@dlasys.net>
On 5/4/06, David H. Lynch Jr. <dhlii@dlasys.net> wrote:
> 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.
>
Yes I am finding this out. It's a long journey! :)
Most of the issues I have to deal with are systems that are already up
and running in the PPC world and I come in afterwords to clean up. So
for example, right now I think I have a DMA problem that is crashing
my PPC and rebooting the system.
To be sure, I would love to step over a few instructions and slow the
world down a bit. That's why I was going to setup kgdb or something
like that.
Thanks.
-stv
> 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 n=
umerous to list.
>
>
next prev parent reply other threads:[~2006-05-04 19:51 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) [this message]
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=b4b98b690605041251s40f88731i1edfdfb324da38b4@mail.gmail.com \
--to=netstv@gmail.com \
--cc=dhlii@comcast.net \
--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).