From: "Torsten Polle" <Torsten.Polle@gmx.de>
To: mjw@redhat.com
Cc: systemtap@sourceware.org
Subject: Re: Prelinking on ARM with Debug Link
Date: Tue, 01 Dec 2015 07:26:00 -0000 [thread overview]
Message-ID: <trinity-fc63a04f-3168-4a79-a28f-9b87fa36ae89-1448954804873@3capp-gmx-bs38> (raw)
Hi Mark,
> Torsten Polle writes
>
> Hi Mark,
>
> Mark Wielaard writes:
>> On Fri, Nov 27, 2015 at 04:06:14PM +0100, Mark Wielaard wrote:
>>> On Fri, Nov 27, 2015 at 01:57:31PM +0100, Torsten Polle wrote:
>>> > In file included from /tmp/stap/taptrek_src.c:6010:0:
>>> > /tmp/stap/stap-symbols.h:95902:1: error: large integer implicitly truncated to unsigned type [-Werror=overflow]
>>>
>>> But the stap-symbols.h file has only 8107 lines.
>
>> If you happen to know which library it is that causes the issue, then
>> it would be beneficial to also have the output of eu-readelf -Sl for
>> both the main and debug file.
>
>> And maybe the stap -vv output of the script to know which files and
>> probes are used.
>
>> Thanks,
>> Mark
>
> thanks for the support.
>
> I'll provide you with a reproduction scenario that is much smaller.
>
> Kind Regards,
> Torsten
please find a less complex example attached.
The output of readelf -Sl for the affected library.
libc-2.18.so.txt
The library is using a debug link to link to a file with the debug information.
libc-2.18.so.debug.txt
The command to run the script "taptrek_run_ZIX2.stp" is stored in "cmd.sh".
The output of executing "cmd.sh" is in "cmd-output.txt".
The folder "stap" contains the result of the stap run. I only removed
the already compiled object files to keep the size small.
Thanks,
Torsten
next reply other threads:[~2015-12-01 7:26 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-01 7:26 Torsten Polle [this message]
-- strict thread matches above, loose matches on Subject: below --
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
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
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
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-fc63a04f-3168-4a79-a28f-9b87fa36ae89-1448954804873@3capp-gmx-bs38 \
--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).