[prev in list] [next in list] [prev in thread] [next in thread]
List: oprofile-list
Subject: Re: determining application names for mappings
From: John Levon <levon () movementarian ! org>
Date: 2002-08-01 14:51:05
[Download RAW message or body]
On Thu, Aug 01, 2002 at 05:06:52PM -0400, William Cohen wrote:
> How does the oprofile daemon determine the application name (path to
> executable)? Is the code in oprofiled just assuming that the first entry
> in /proc/nnnn/maps (where nnnn is the pid) is the path the the
> executable?
That's what we did. I even managed to misread the procfs code and remove
the FIXME mentioning /exe link.
> If it is just assuming the first entry in /proc/nnnn/maps
> has the path to the executable, this is likely to break. It would be
> more reliable to get this information from /proc/nnnn/exe with a readlink.
... until recently when phe fixed it to do this because X was breaking
the assumption. This change is in ooprofile 0.3
regards
john
--
"The simpler it is, the harder it is."
- Tim Van Holder
[prev in list] [next in list] [prev in thread] [next in thread]
Configure |
About |
News |
Add a list |
Sponsored by KoreLogic