From: naresh kamboju <naresh.kernel@gmail.com>
To: Eugeniy Meshcheryakov <eugen@debian.org>
Cc: systemtap@sources.redhat.com,
"Frank Ch. Eigler" <fche@redhat.com>,
Dave Brolley <brolley@redhat.com>,
David Smith <dsmith@redhat.com>,
Masami Hiramatsu <mhiramat@redhat.com>
Subject: Re: Integer constant is too large for 'long' type
Date: Thu, 26 Nov 2009 07:04:00 -0000 [thread overview]
Message-ID: <f5a7b3810911252304w26b051der539ff0e1aec312e2@mail.gmail.com> (raw)
In-Reply-To: <20091116182307.GA6377@localhost.localdomain>
Hi,
The following issue was noticed
Issue:
/tmp/stapkpgLTm/stap-symbols.h:60600: error: integer constant is too
large for 'long' type
/tmp/stapkpgLTm/stap-symbols.h:60600: error: large integer implicitly
truncated to unsigned type
>> http://www.mail-archive.com/debian-bugs-dist@lists.debian.org/msg690166.html
>>This patch was needed for kernels with CONFIG_RELOCATABLE set.
I am not sure about the CONFIG_RELOCATABLE in ARM Kernels.
Is this config option only for X86 and PowerPC?
I have made following changes for the ARM architecture to over come
the above build issues.
Index: b/translate.cxx
===================================================================
--- a/translate.cxx
+++ b/translate.cxx
@@ -4905,8 +4905,13 @@ dump_unwindsyms (Dwfl_Module *m,
correct either. We may instead need a relocation basis different
from _stext, such as __start_notes. */
if (modname == "kernel")
+#if 0
c->output << ".build_id_offset = 0x" << hex << build_id_vaddr -
(base + extra_offset)
<< dec << ",\n";
+#else
+ c->output << ".build_id_offset = 0x" << hex << build_id_vaddr
+ << dec << ",\n";
+#endif
else
c->output << ".build_id_offset = 0x" << hex
<< build_id_vaddr - base
>That's only the build issue. Does the code *run* though, meaning does
>it actually verify the buildid bits at virtual address 0x0-ish on your
arm kernel? I suspect not.
I am not sure about how to verify the results. Please help me out in
this context.
However, I am able to build and staprun is working fine.
#staprun five.ko
Best regards
Naresh Kamboju
On Mon, Nov 16, 2009 at 11:53 PM, Eugeniy Meshcheryakov
<eugen@debian.org> wrote:
> 16 листопада 2009 о 21:14 +0530 naresh kamboju написав(-ла):
>> However, I have back ported this patch and able to resolve the build
>> issue on ARM.
>
> I assume that this means that you have reverted the patch. Is it
> possible to load generated modules after that? Or does this only fix
> compilation?
>
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.4.10 (GNU/Linux)
>
> iEYEARECAAYFAksBmIsACgkQKaC6+zmozOIVmwCgk361WR6KPs2Lvf+OSTEBcpdu
> TZ0An08rPalwgz9O2D6rqjDMTrz6adBM
> =cxSs
> -----END PGP SIGNATURE-----
>
>
next prev parent reply other threads:[~2009-11-26 7:04 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-11-05 8:40 naresh kamboju
2009-11-05 8:47 ` Mark Wielaard
2009-11-05 10:42 ` naresh kamboju
2009-11-05 14:56 ` naresh kamboju
2009-11-05 15:25 ` Frank Ch. Eigler
2009-11-05 15:34 ` naresh kamboju
[not found] ` <20091105153606.GC21665@redhat.com>
[not found] ` <f5a7b3810911050748h1d4e82ft4d5af4a5b14d6d49@mail.gmail.com>
2009-11-05 15:54 ` Frank Ch. Eigler
2009-11-05 16:09 ` naresh kamboju
2009-11-16 15:45 ` naresh kamboju
2009-11-16 18:16 ` Eugeniy Meshcheryakov
2009-11-16 18:24 ` Eugeniy Meshcheryakov
2009-11-26 7:04 ` naresh kamboju [this message]
2009-11-17 20:02 ` Frank Ch. Eigler
2009-11-18 14:51 ` naresh kamboju
2009-11-06 12:13 ` Mark Wielaard
2009-11-06 14:36 ` naresh kamboju
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=f5a7b3810911252304w26b051der539ff0e1aec312e2@mail.gmail.com \
--to=naresh.kernel@gmail.com \
--cc=brolley@redhat.com \
--cc=dsmith@redhat.com \
--cc=eugen@debian.org \
--cc=fche@redhat.com \
--cc=mhiramat@redhat.com \
--cc=systemtap@sources.redhat.com \
/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 read-only IMAP folder(s) and NNTP newsgroup(s).