From: Stefan Schulze Frielinghaus <stefan@seekline.net>
To: Michal Svoboda <michal.svoboda@agents.felk.cvut.cz>
Cc: selinux <selinux@tycho.nsa.gov>
Subject: Re: how to trace an avc denial
Date: Mon, 01 Feb 2010 21:36:14 +0100 [thread overview]
Message-ID: <1265056574.4834.6.camel@localhost> (raw)
In-Reply-To: <20100130213222.GO1639@myhost.felk.cvut.cz>
On Sa, 2010-01-30 at 22:32 +0100, Michal Svoboda wrote:
[...]
> strace/ltrace should almost universally help, though sometimes you need
> extra privileges to maintain a ptrace() over process tree. When you're
> not starting from shell, strace the 'launcher' program, ie. the one that
> acts on the menu entry and/or hotkey you use to run it.
>
> If the trace itself does not make the cause evident, it should at least
> help you narrow down the relevant parts of source code.
Yeah, I gave strace another shot and this time I got what I needed:
4513 getppid() = 1
4513 readlink("/proc/1/exe", 0xbf824ddc, 512) = -1 EACCES (Permission
denied)
A grep after getppid in the sources of pidgin showed me the line of
interest ;-)
Thanks Michal and Stephen for your suggestions.
cheers,
Stefan
--
This message was distributed to subscribers of the selinux mailing list.
If you no longer wish to subscribe, send mail to majordomo@tycho.nsa.gov with
the words "unsubscribe selinux" without quotes as the message.
next prev parent reply other threads:[~2010-02-01 20:36 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-30 17:43 how to trace an avc denial Stefan Schulze Frielinghaus
2010-01-30 21:32 ` Michal Svoboda
2010-02-01 20:36 ` Stefan Schulze Frielinghaus [this message]
2010-02-01 14:29 ` Stephen Smalley
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=1265056574.4834.6.camel@localhost \
--to=stefan@seekline.net \
--cc=michal.svoboda@agents.felk.cvut.cz \
--cc=selinux@tycho.nsa.gov \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.