From: "Bill F" <list.mail.for.bill@gmail.com>
To: linuxppc-embedded@ozlabs.org
Subject: Re: Breakpoint is not hitting for Kernel Debugging
Date: Tue, 4 Sep 2007 14:07:10 +1000 [thread overview]
Message-ID: <7c1681440709032107u3feb0684x34dcf44b5e43616@mail.gmail.com> (raw)
In-Reply-To: <F3D55679E1DCFF49A57570501B70475F070D83BC@CL5EXBE04.ad2.softcom.biz>
On 9/4/07, dnl <ssaravanan@mail2web.com> wrote:
> I enabled the following options in Kernel for kernel Debugging,
> CONFIG_BDI_SWITCH=y CONFIG_DEBUG_INFO=y under kernel hacking and MMU XALT in
> BDI config file. After uboot initialization I fixed break point at
> start_kernel(0xc02784bc), and then I booted the kernel. Without breaking at
> start_kernel, it came to login prompt. Please find attached config file with
> this mail. Could anybody help me to solve this problem?
Hi Saravanan,
Try adding this line to your BDI config to clear/invalidate the page
table base address so that the MMU translation works before the MMU
has been initialised.
;; Following is to clear the page table base address
WM32 0x000000f0 0x00000000
Make sure that you reload the BDI config, I use the the BDI "BOOT"
command to do this.
Are you obtaining the start_kernel address from your kernel System.map
file and setting the breakpoint using the BDI command "BI 0xc02784bc"
or are you using a gdb debugger frontend ?
Bill
next prev parent reply other threads:[~2007-09-04 4:07 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-09-03 14:02 Breakpoint is not hitting for Kernel Debugging dnl
2007-09-03 19:20 ` Dan Malek
2007-09-04 4:07 ` Bill F [this message]
2007-09-05 13:27 ` Detlev Zundel
2007-09-05 16:31 ` Dan Malek
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=7c1681440709032107u3feb0684x34dcf44b5e43616@mail.gmail.com \
--to=list.mail.for.bill@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).