From: Mark Wielaard <mjw@redhat.com>
To: elfutils-devel@lists.fedorahosted.org
Subject: Re: 0.161 elfutils test are failing on Linux Arch
Date: Fri, 16 Jan 2015 17:02:27 +0100 [thread overview]
Message-ID: <1421424147.26117.37.camel@bordewijk.wildebeest.org> (raw)
In-Reply-To: CAOMFOmUbyApy5pPf660d=4rSWsqx2Nja5kFiLZN=S6cJ7wBYQw@mail.gmail.com
[-- Attachment #1: Type: text/plain, Size: 1654 bytes --]
On Fri, 2015-01-16 at 06:12 -0800, Anatol Pomozov wrote:
> On Thu, Jan 15, 2015 at 3:06 AM, Mark Wielaard <mjw@redhat.com> wrote:
> > Awesome! BTW. Which architecture and what are the two SKIPPED tests?
> >
> I have x86_64 and the skipped tests are
>
> SKIP: run-backtrace-native-core.sh
> SKIP: run-backtrace-native-core-biarch.sh
OK. That would happen if the system doesn't create core dump files in
the working directory. Those tests try to create a core dump and then
inspect it. They SKIP the test if the core file isn't generated for some
reason.
> > I'll try to code something up and if you could test that, that would be
> > awesome.
> >
> Thanks. The patch works great. All tests are passed now.
Thanks for testing. I pushed the patch to master.
> > But... This is really workarounds for the testcases. Then we know the
> > functionality works as intended. Except when a real user uses the dwfl
> > attach library calls or eu-stack binary...
> >
> > So we probably need to figure out how to really fix this. How do other
> > tools and libraries work? What if a user wants to see why firefox is
> > wonky and does a strace -p $(pidof firefox) or gstack $(pidof firefox).
> > Are those tools also broken by default on Arch? Or do they use some
> > other trick to work properly?
> >
>
> I get "Operation not permitted", my understanding that in this case user
> should use sudo.
Hmmm. That sounds pretty bad from a security perspective. So you
basically have to have root to do any process introspection? That means
eu-stack -p probably also only works when run with root privileges.
Cheers,
Mark
next reply other threads:[~2015-01-16 16:02 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-16 16:02 Mark Wielaard [this message]
-- strict thread matches above, loose matches on Subject: below --
2015-01-20 14:30 Mark Wielaard
2015-01-17 14:04 Dmitry V. Levin
2015-01-16 17:21 Josh Stone
2015-01-16 14:12 Anatol Pomozov
2015-01-15 12:56 Mark Wielaard
2015-01-15 11:06 Mark Wielaard
2015-01-14 21:30 Anatol Pomozov
2015-01-14 21:16 Mark Wielaard
2015-01-14 19:51 Anatol Pomozov
2015-01-14 19:41 Mark Wielaard
2015-01-14 19:19 Anatol Pomozov
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=1421424147.26117.37.camel@bordewijk.wildebeest.org \
--to=mjw@redhat.com \
--cc=elfutils-devel@lists.fedorahosted.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).