From: Mark Wielaard <mjw@redhat.com>
To: Torsten Polle <Torsten.Polle@gmx.de>
Cc: systemtap@sourceware.org
Subject: Re: Prelinking on ARM with Debug Link
Date: Wed, 10 Feb 2016 20:35:00 -0000 [thread overview]
Message-ID: <1455136517.7606.107.camel@redhat.com> (raw)
In-Reply-To: <3855EE25-54F2-47FB-88A8-FF1EC3963C06@gmx.de>
On Wed, 2016-02-10 at 21:12 +0100, Torsten Polle wrote:
> > Am 10.02.2016 um 17:17 schrieb Mark Wielaard <mjw@redhat.com>:
> > It has been some time since I hacked on this code, so I don't
> > immediately know what is going on. It would be nice to have a somewhat
> > simpler reproducer. You use a large stap script using guru mode mixing
> > user and kernel probes. Is all that really necessary to replicate the
> > issue? Is the issue only triggered by the cross compiling?
>
> Do you mean the example in my original mail or do you refer to the much simpler example from [1]?
Maybe I am not reading the simpler example correctly.
But it looked like it was still mixing user and kernel probes, used guru
mode and cross compiling. Are all of those factors needed to trigger the
bug?
If at all possible just one simple probe against libc.so to show what is
going wrong would be ideal.
Thanks,
Mark
next prev parent reply other threads:[~2016-02-10 20:35 UTC|newest]
Thread overview: 38+ messages / expand[flat|nested] mbox.gz Atom feed top
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 [this message]
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
2016-04-13 14:36 ` Aw: " Torsten Polle
-- strict thread matches above, loose matches on Subject: below --
2015-12-01 7:26 Torsten Polle
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=1455136517.7606.107.camel@redhat.com \
--to=mjw@redhat.com \
--cc=Torsten.Polle@gmx.de \
--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).