From: "Xu Yang" <risingsunxy@googlemail.com>
To: "Jesper Juhl" <jesper.juhl@gmail.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: how to add debug information into the vmlinux
Date: Sat, 18 Aug 2007 21:49:50 +0200 [thread overview]
Message-ID: <ab40e9c0708181249l7389c300sd68964e22bf262a9@mail.gmail.com> (raw)
In-Reply-To: <9a8748490708171430u2be506canf640d5c8c97149c6@mail.gmail.com>
Hi Jesper,
I tried as what you told me. and the vmlinux does contain debug
information. but the start address of this vmlinux is 0xc0008000. when
I tried to run this vmlinux, the program always exit at 0x80a0. I
checked out that here is the place mmu is turned on.
so I used objcopy --change-addresses 0x40000000 to change the start
address of the vmlinux, and the program goes further.but the debug
information disappeared.
how to handle this? (making the program running and debug information available)
thanks,
regards,
yang
2007/8/17, Jesper Juhl <jesper.juhl@gmail.com>:
> On 17/08/07, Xu Yang <risingsunxy@googlemail.com> wrote:
> > Hello everyone,
> >
> > I am trying to port kernel 2.6.19 onto my system.so I need the c code
> > , which can show me where the program is running. I add -g when I
> > compile it.
> >
> You shouldn't need to do that manually, simply go into "make
> menuconfig", enter the "Kernel hacking" menu and select the "Kernel
> debugging" and "Compile the kernel with debug info" options.
> You may also want to enable "Compile the kernel with frame pointers"
> and various other options in that menu to get more debug info.
>
>
> --
> Jesper Juhl <jesper.juhl@gmail.com>
> Don't top-post http://www.catb.org/~esr/jargon/html/T/top-post.html
> Plain text mails only, please http://www.expita.com/nomime.html
>
next prev parent reply other threads:[~2007-08-18 19:50 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-08-17 20:49 Xu Yang
2007-08-17 21:30 ` Jesper Juhl
2007-08-18 19:49 ` Xu Yang [this message]
2007-08-18 19:54 ` Jan Engelhardt
2007-08-18 20:01 ` Xu Yang
2007-08-18 21:10 ` Jan Engelhardt
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=ab40e9c0708181249l7389c300sd68964e22bf262a9@mail.gmail.com \
--to=risingsunxy@googlemail.com \
--cc=jesper.juhl@gmail.com \
--cc=linux-kernel@vger.kernel.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
all inboxes | Powered by JetHome®