Re: Integer constant is too large for 'long' type

[naresh kamboju <naresh dot kernel at gmail dot com>]

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

Please provide your comments.

Best regards
Naresh Kamboju