/proc/PID/exe is a symlink to a filename, not to a file. So you can't tell just by looking at it whether the executable stored at (eg) /usr/sbin/apache is really the one that is running. Better, I think, to do something like this pseudo-code: 
foreach PID
  lsof -p PID | grep FILENAME
    and parse out the inode number
  stat FILENAME
  do the inodes match?

[download]
still not foolproof, of course. It's also far more portable to use utilities like lsof than to grovel around in /proc which doesn't even exist on some systems. But on Linux/x86 (and presumably Linux/others too) all the information you need is in /proc/PID/maps.

In reply to Re: Checking for unlinked process executables by DrHyde
in thread Checking for unlinked process executables by Corion

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post, it's "PerlMonks-approved HTML":


  • Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
  • Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
  • Read Where should I post X? if you're not absolutely sure you're posting in the right place.
  • Please read these before you post! —
  • Posts may use any of the Perl Monks Approved HTML tags:
    a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
  • You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
            For:     Use:
    & &amp;
    < &lt;
    > &gt;
    [ &#91;
    ] &#93;
  • Link using PerlMonks shortcuts! What shortcuts can I use for linking?
  • See Writeup Formatting Tips and other pages linked from there for more info.