linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Wolfgang Denk <wd@denx.de>
To: Marco Schramel <Schramel.Linux@go.bartec.de>
Cc: "PPC_LINUX" <linuxppc-embedded@lists.linuxppc.org>
Subject: Re: BDI kernel debug
Date: Tue, 06 Jul 2004 20:18:26 +0200	[thread overview]
Message-ID: <20040706181831.52416C109F@atlas.denx.de> (raw)
In-Reply-To: Your message of "Tue, 06 Jul 2004 13:31:08 +0200." <200407061331.08613.Schramel.Linux@go.bartec.de>


In message <200407061331.08613.Schramel.Linux@go.bartec.de> you wrote:
>
> i have some problems with debugging my kernel. This is the first time i use bdi for kernel debugging. ELDK 3.0 is my toolchain (Target 8270).
...
> Are there some options in the kernel or in the gdb to set ?

Did you enable CONFIG_DEBUG_KERNEL in your kernel configuration?

Did you read the FAQ section of the DULG, especially
http://www.denx.de/twiki/bin/view/DULG/HowToDebugLinuxExceptions
and
http://www.denx.de/twiki/bin/view/DULG/HowToSingleStepThroughRFIInstruction

Best regards,

Wolfgang Denk

--
Software Engineering:  Embedded and Realtime Systems,  Embedded Linux
Phone: (+49)-8142-4596-87  Fax: (+49)-8142-4596-88  Email: wd@denx.de
Death, when unnecessary, is a tragic thing.
	-- Flint, "Requiem for Methuselah", stardate 5843.7

** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/

  reply	other threads:[~2004-07-06 18:18 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-07-06 11:31 BDI kernel debug Marco Schramel
2004-07-06 18:18 ` Wolfgang Denk [this message]
2004-07-07  5:01   ` Marco Schramel
2004-07-07 11:42 ` Fahd Abidi
2004-07-07 11:52   ` Marco Schramel
     [not found] <81C69D96BDD30640952C7A404004AA250C2CA8@h0007e95d9fa7.ne.client2.attbi.com>
2004-07-07 13:07 ` Fahd Abidi
2004-07-08 14:03   ` Marco Schramel

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=20040706181831.52416C109F@atlas.denx.de \
    --to=wd@denx.de \
    --cc=Schramel.Linux@go.bartec.de \
    --cc=linuxppc-embedded@lists.linuxppc.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).