From: naresh kamboju <naresh.kernel@gmail.com>
To: "Frank Ch. Eigler" <fche@redhat.com>
Cc: Mark Wielaard <mjw@redhat.com>, systemtap@sources.redhat.com
Subject: Re: Integer constant is too large for 'long' type
Date: Thu, 05 Nov 2009 15:34:00 -0000 [thread overview]
Message-ID: <f5a7b3810911050734m665e5005r4152211922dd5a37@mail.gmail.com> (raw)
In-Reply-To: <20091105152546.GB21665@redhat.com>
Hi Frank,
On Thu, Nov 5, 2009 at 8:55 PM, Frank Ch. Eigler <fche@redhat.com> wrote:
> Hi -
>
> On Thu, Nov 05, 2009 at 08:26:26PM +0530, naresh kamboju wrote:
>> [...]
>> # stap -a arm -B CROSS_COMPILE=/usr/local/arm/cross/devel/bin/arm-dev-
>> -p4 -vv -k -r 2.6.29.4-alp_nl-kzm-arm11-g2542246 -m five five.stp
>> [...]
>> Session arch: arm release: 2.6.29.4-kzm-arm11-g2542246
>> dump_unwindsyms kernel index=0 base=0x0
>> Found build-id in kernel, length 20, end at 0x24
>> [...]
>> .build_id_bits =
>> "\xd9\x1d\x7e\x1f\x5a\x79\xbc\xe0\x43\x34\x49\x69\x21\x59\x34\x1d\xbe\xe5\x8b\x33",
>> .build_id_len = 20,
>> .build_id_offset = 0xffffffff3fff8024,
>
> It seems as though the memory/section layout of the arm kernel is
> rather different from what we've seen.
ok.
> Can you send over some
> "readelf {-S,-l,-n} ..../vmlinux" output?
I am not clear about above line.
could give me in a detail steps, so that i can share build/results logs.
Best regards,
Naresh Kamboju
>
> - FChE
>
next prev parent reply other threads:[~2009-11-05 15:34 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 [this message]
[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=f5a7b3810911050734m665e5005r4152211922dd5a37@mail.gmail.com \
--to=naresh.kernel@gmail.com \
--cc=fche@redhat.com \
--cc=mjw@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).