qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Paul Brook <paul@codesourcery.com>
To: qemu-devel@nongnu.org
Cc: Riku Voipio <riku.voipio@iki.fi>
Subject: Re: [Qemu-devel] [PATCH] linux-user: identify running binary in /proc/self/exe
Date: Mon, 19 Jan 2009 15:57:26 +0000	[thread overview]
Message-ID: <200901191557.27453.paul@codesourcery.com> (raw)
In-Reply-To: <20090119153008.GA20882@kos.to>

On Monday 19 January 2009, Riku Voipio wrote:
> Some applications like to test /proc/self/exe to find
> out who they are. Fake the result of readlink() for
> them.

> +    exec_path = argv[optind];

Won't this give the wrong answer when the binary is invoked using a relative 
path or a symlink? On my system /proc/self/exe is always an absolute path to 
an actual file.

Paul

  reply	other threads:[~2009-01-19 15:57 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-01-19 15:30 [Qemu-devel] [PATCH] linux-user: identify running binary in /proc/self/exe Riku Voipio
2009-01-19 15:57 ` Paul Brook [this message]
2009-01-20 16:01   ` Riku Voipio
2009-01-26 19:07     ` Riku Voipio
2009-01-30 20:10       ` Aurelien Jarno

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=200901191557.27453.paul@codesourcery.com \
    --to=paul@codesourcery.com \
    --cc=qemu-devel@nongnu.org \
    --cc=riku.voipio@iki.fi \
    /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 NNTP newsgroup(s).