From: Scott Wood <scottwood@freescale.com>
To: Steve Heflin <sheflin@newagemicro.com>
Cc: linuxppc-embedded@ozlabs.org
Subject: Re: Sequoia build with KDBG
Date: Fri, 29 Feb 2008 16:58:45 -0600 [thread overview]
Message-ID: <47C88E25.2050306@freescale.com> (raw)
In-Reply-To: <20080229223046.1B332DDE0A@ozlabs.org>
Steve Heflin wrote:
> I assumed that because I've always needed a debugger when
> implementing kernel level components. Since you've implemented kernel
> level support for several 44x processors, I just assumed that you
> needed kdbg at some point. So you're saying that your additions
> worked right out of the gate and you never needed a debugger? You're my hero!
There are ways of debugging that don't involve a debugger.
-Scott
next prev parent reply other threads:[~2008-02-29 22:58 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-21 21:33 MODPOST section mismatches Steve Heflin
2008-02-22 16:12 ` Steve Heflin
2008-02-22 20:52 ` Josh Boyer
2008-02-22 22:26 ` Steve Heflin
2008-02-22 22:36 ` Josh Boyer
2008-02-22 23:07 ` Steve Heflin
2008-02-23 0:30 ` Josh Boyer
2008-02-23 0:38 ` Steve Heflin
2008-02-29 21:34 ` Sequoia build with KDBG Steve Heflin
[not found] ` <200802292133.m1TLXqv3012273@e36.co.us.ibm.com>
2008-02-29 21:35 ` Josh Boyer
2008-02-29 22:31 ` Steve Heflin
2008-02-29 22:58 ` Scott Wood [this message]
2008-02-29 23:28 ` Jon Loeliger
2008-03-01 0:16 ` Wolfgang Denk
2008-03-01 1:48 ` Steve Heflin
[not found] ` <200802292230.m1TMUk4I005462@e31.co.us.ibm.com>
2008-02-29 22:51 ` Josh Boyer
[not found] ` <200803010023.m210NHwr011345@e2.ny.us.ibm.com>
2008-03-01 2:30 ` Josh Boyer
2008-03-01 2:55 ` Steve Heflin
2008-03-02 14:47 ` Wolfgang Denk
2008-03-01 5:02 ` Olof Johansson
2008-03-01 13:13 ` Josh Boyer
2008-03-01 15:57 ` Olof Johansson
-- strict thread matches above, loose matches on Subject: below --
2008-03-01 0:36 Steve Heflin
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=47C88E25.2050306@freescale.com \
--to=scottwood@freescale.com \
--cc=linuxppc-embedded@ozlabs.org \
--cc=sheflin@newagemicro.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.