From: Jeff Dike <jdike@addtoit.com>
To: BlaisorBlade <blaisorblade_spam@yahoo.it>
Cc: user-mode-linux-devel@lists.sourceforge.net
Subject: [uml-devel] Re: Vmlinux - linux linking stages & /proc/kallsyms empty
Date: Tue, 30 Mar 2004 16:38:03 -0500 [thread overview]
Message-ID: <200403302138.i2ULc3Ll004220@ccure.user-mode-linux.org> (raw)
In-Reply-To: Your message of "Tue, 30 Mar 2004 19:25:02 +0100." <200403302025.02276.blaisorblade_spam@yahoo.it>
blaisorblade_spam@yahoo.it said:
> This because the vmlinux link script is wrong (you rejected the patch
> I sent you time ago, was in the patchset). But kallsyms must contain
> the true addresses of the kernel symbols; since they change between
> vmlinux and linux (if they didn't change, the second step would be
> useless), they cannot be correct. I think that even System.map
> symbols do not match.
I didn't reject it so much as I put it aside for the moment because I didn't
understand it.
Your explanations, then and now, make sense, so I'm going to have another
look at it for my next 2.6 patch.
Jeff
-------------------------------------------------------
This SF.Net email is sponsored by: IBM Linux Tutorials
Free Linux tutorial presented by Daniel Robbins, President and CEO of
GenToo technologies. Learn everything from fundamentals to system
administration.http://ads.osdn.com/?ad_id=1470&alloc_id=3638&op=click
_______________________________________________
User-mode-linux-devel mailing list
User-mode-linux-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/user-mode-linux-devel
next prev parent reply other threads:[~2004-03-30 21:01 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-03-30 18:25 [uml-devel] Vmlinux - linux linking stages & /proc/kallsyms empty BlaisorBlade
2004-03-30 21:38 ` Jeff Dike [this message]
2004-03-31 18:42 ` [uml-devel] " BlaisorBlade
2004-03-31 21:04 ` Jeff Dike
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=200403302138.i2ULc3Ll004220@ccure.user-mode-linux.org \
--to=jdike@addtoit.com \
--cc=blaisorblade_spam@yahoo.it \
--cc=user-mode-linux-devel@lists.sourceforge.net \
/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