From: "Peter Ryser" <Peter.Ryser@xilinx.com>
To: linuxppc-embedded@lists.linuxppc.org
Subject: Re: mmu problems
Date: Thu, 26 Jul 2001 23:53:13 -0700 [thread overview]
Message-ID: <3B610FD9.17F01F88@xilinx.com> (raw)
In-Reply-To: 3B4F412F.99A14D9E@comdev.cc
Hi Adam,
not a solution for your real problem, but I hope it helps anyway.
> Is there any way I can get gcc to annotate the assembly listing with the
> C source
> code? I feel it would help pinpoint what is going on...
objdump --source vmlinux
produces a mixed C/assembly file. Works only if debugging information has been
included in the kernel during compilation.
- Peter
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
prev parent reply other threads:[~2001-07-27 6:53 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-07-13 18:42 mmu problems Adam Wozniak
2001-07-13 20:36 ` Dan Malek
2001-07-16 15:58 ` Adam Wozniak
2001-07-16 16:56 ` Adam Wozniak
2001-07-16 18:10 ` Cal Erickson
2001-07-17 23:29 ` Adam Wozniak
2001-07-27 6:53 ` Peter Ryser [this message]
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=3B610FD9.17F01F88@xilinx.com \
--to=peter.ryser@xilinx.com \
--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).