public inbox for systemtap@sourceware.org
 help / color / mirror / Atom feed
From: naresh kamboju <naresh.kernel@gmail.com>
To: systemtap@sources.redhat.com
Cc: "Frank Ch. Eigler" <fche@redhat.com>
Subject: Integer constant is too large for 'long' type
Date: Thu, 05 Nov 2009 08:40:00 -0000	[thread overview]
Message-ID: <f5a7b3810911050040w573c404ft619d6ebb53edd267@mail.gmail.com> (raw)

Hi,

I have notice following warning for the most of stp example files
under testsuite directory.
Warnings being treated as errors and coming out from the build.


/*******************************************************************/
# stap -a arm -B CROSS_COMPILE=/usr/local/arm/cross/devel/bin/arm-dev-
-p4  -r 2.6.29.4-kzm-arm11-g8de6eff -m five five.stp  -vv
SystemTap translator/driver (version 1.0/0.137 non-git sources)
Copyright (C) 2005-2009 Red Hat, Inc. and others
This is free software; see the source for copying conditions.
Session arch: arm release: 2.6.29.4-kzm-arm11-g8de6eff
Created temporary directory "/tmp/stapBF1Ti1"
Searched '/usr/local/arm/cross/devel/share/systemtap/tapset/*.stp', found 56
Pass 1: parsed user script and 56 library script(s) in 270usr/20sys/340real ms.
probe schedule@kernel/sched.c:4699 kernel reloc=.dynamic pc=0xc0310c84
probe schedule@kernel/sched.c:4699 kernel reloc=.dynamic pc=0xc0310c84
Pass 2: analyzed script: 2 probe(s), 1 function(s), 0 embed(s), 0
global(s) in 400usr/20sys/509real ms.
function recursion-analysis: max-nesting 0 non-recursive
probe_1784 locks nothing
probe_1785 locks nothing
stap_dwarf_probe module[7]
stap_dwarf_probe section[7]
stap_dwarf_probe pp[59]
dump_unwindsyms kernel index=0 base=0x0
Found build-id in kernel, length 20, end at 0x24
Found kernel _stext extra offset 0xc0008000
Pass 3: translated to C into "/tmp/stapBF1Ti1/five.c" in
570usr/20sys/601real ms.
Running make -C "/lib/modules/2.6.29.4-kzm-arm11-g8de6eff/build"
M="/tmp/stapBF1Ti1" ARCH="arm"
"CROSS_COMPILE=/usr/local/arm/cross/devel/bin/arm-dev-" modules
--no-print-directory
  CC [M]  /tmp/stapBF1Ti1/five.o
cc1: warnings being treated as errors
In file included from /tmp/stapBF1Ti1/five.c:754:
/tmp/stapBF1Ti1/stap-symbols.h:66980: error: integer constant is too
large for 'long' type
/tmp/stapBF1Ti1/stap-symbols.h:66980: error: large integer implicitly
truncated to unsigned type
make[1]: *** [/tmp/stapBF1Ti1/five.o] Error 1
make: *** [_module_/tmp/stapBF1Ti1] Error 2
Pass 4: compiled C into "five.ko" in 3210usr/900sys/4604real ms.
Pass 4: compilation failed.  Try again with another '--vp 0001' option.
Running rm -rf /tmp/stapBF1Ti1
/*******************************************************************/
SystemTap-1.0
elfutils-0.137
gcc version 4.3.3
glibc-2.9
Kernel 2.6.29
/*******************************************************************/

Please provide if you any information related to this.


Best regards,
Naresh Kamboju

             reply	other threads:[~2009-11-05  8:40 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-11-05  8:40 naresh kamboju [this message]
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
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=f5a7b3810911050040w573c404ft619d6ebb53edd267@mail.gmail.com \
    --to=naresh.kernel@gmail.com \
    --cc=fche@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).