From: "Torsten Polle" <Torsten.Polle@gmx.de>
To: "Mark Wielaard" <mjw@redhat.com>
Cc: systemtap@sourceware.org
Subject: Re: Prelinking on ARM with Debug Link
Date: Fri, 27 Nov 2015 12:57:00 -0000 [thread overview]
Message-ID: <trinity-3900ad7c-e8cf-4ef7-a056-05aab57ef83e-1448629051883@3capp-gmx-bs04> (raw)
In-Reply-To: <1448611496.7609.80.camel@redhat.com>
[-- Attachment #1: Type: text/plain, Size: 1420 bytes --]
> Gesendet: Freitag, 27. November 2015 um 09:04 Uhr
> Von: "Mark Wielaard" <mjw@redhat.com>
> An: "Torsten Polle" <Torsten.Polle@gmx.de>
> Cc: systemtap@sourceware.org
> Betreff: Re: Prelinking on ARM with Debug Link
> On Thu, 2015-11-26 at 23:04 +0100, Torsten Polle wrote:
> > Mark Wielaard writes:\
> > > On Wed, 2015-11-25 at 21:52 +0100, Torsten Polle wrote:
> > >> Here I have a problem to compile my probes when I want to include unwind information.
> > >>
> > >> The error message is as follow:
> > >>
> > >> In file included from /tmp/stap/taptrek_src.c:6010:0:
> > >> /tmp/stap/stap-symbol.h:95831:1: error: large integer implicitly truncated to unsigned type [-Werror=overflow]
> > >> },
> > >> ^
> > >>
> > >> The offending line in stap-symbols.h looks as follows:
> > >> .sec_load_offset = 0xffffffffffffebc0 /* 4dec8000 4dec9440*/
> > >>
> > >> The line includes debug output, because I checked the code in
> > >> translate.cxx that generates this output and wanted to understand
> > >> what is going wrong.
>
> What is the stap command line and script you are using?
> Could you post (more of the) taptrek_src.c and stap-symbols.h for
> context?
>
> Thanks,
> Mark
Hi Mark,
Please find attached the requested information.
I've stripped down the output of SystemTap in folder stap.
commandline.txt contains the full command line.
taptrek_run_izA4.stp contains the script used.
Kind Regards,
Torsten
[-- Attachment #2: prelinking.tar.bz2 --]
[-- Type: application/octet-stream, Size: 74446 bytes --]
next prev parent reply other threads:[~2015-11-27 12:57 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-25 20:52 Torsten Polle
2015-11-26 10:33 ` Mark Wielaard
2015-11-26 22:05 ` Torsten Polle
2015-11-27 8:05 ` Mark Wielaard
2015-11-27 12:57 ` Torsten Polle [this message]
2015-11-27 15:06 ` Mark Wielaard
2015-11-27 16:34 ` Mark Wielaard
2015-11-27 20:08 ` Torsten Polle
2015-11-27 20:01 ` Torsten Polle
2015-11-30 19:26 ` David Smith
2015-12-01 20:10 ` Torsten Polle
2015-12-10 19:00 ` David Smith
2015-12-10 19:45 ` Torsten Polle
2015-12-01 7:26 Torsten Polle
2015-12-01 19:29 Torsten Polle
2016-02-09 20:55 ` Torsten Polle
2016-02-10 16:17 ` Mark Wielaard
2016-02-10 20:12 ` Torsten Polle
2016-02-10 20:35 ` Mark Wielaard
2016-02-11 10:49 ` Aw: " Torsten Polle
2016-02-16 10:08 ` Mark Wielaard
2016-02-16 20:46 ` Torsten Polle
2016-02-18 16:21 ` Mark Wielaard
2016-02-22 21:45 ` Torsten Polle
2016-02-23 16:46 ` Mark Wielaard
2016-02-23 22:16 ` Torsten Polle
2016-02-28 20:51 ` Torsten Polle
2016-03-30 20:05 ` Torsten Polle
2016-04-01 13:07 ` Mark Wielaard
2016-04-01 21:19 ` Torsten Polle
2016-04-05 13:44 ` Mark Wielaard
2016-04-06 20:45 ` Torsten Polle
2016-04-06 21:56 ` Mark Wielaard
2016-04-11 18:47 ` Torsten Polle
2016-04-11 21:02 ` Mark Wielaard
2016-04-12 20:26 ` Torsten Polle
2016-04-13 9:25 ` Mark Wielaard
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=trinity-3900ad7c-e8cf-4ef7-a056-05aab57ef83e-1448629051883@3capp-gmx-bs04 \
--to=torsten.polle@gmx.de \
--cc=mjw@redhat.com \
--cc=systemtap@sourceware.org \
/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).