"Fossies" - the Fresh Open Source Software Archive

Member "mpr-2.8/FAQ" (7 Jun 2005, 1587 Bytes) of package /linux/misc/old/mpr-2.8.tar.gz:

    1 1. When I try to look at the log file using mprmap, I get weird results.
    2 
    3 2. How difficult would it be to add support to mpr to detect memory access
    4    violations like the commercial tool Purify(tm) does ?
    5 
    6 3. Why don't you rewrite the whole thing in C for speed ?
    7 
    8 --
    9 
   10 1. When I try to look at the log file using mprmap, I get weird results.
   11 
   12 You should ensure that the executable program you specify as an argument to
   13 mprmap is the same version that was used to create the log file.  Otherwise,
   14 the mapping from the program counters that are stored in the log file to
   15 function names in the executable may not be correct, in which case you may
   16 get very misleading output from mprmap.  Also, if you are using mprmap with a
   17 stripped executable, then the mapping from program counter to function names
   18 may also not be valid (mprmap will warn you if you specify a stripped
   19 executable).
   20 
   21 --
   22 
   23 2. How difficult would it be to add support to mpr to detect memory access
   24    violations like the commercial tool Purify(tm) does ?
   25 
   26 Very difficult.  mpr was designed to detect memory leaks and memory allocation
   27 statistics only, which is a MUCH simpler task than what tools like Purify(tm)
   28 do.  If you are interested in a freely available tool which tries to detect
   29 memory access violations on x86-linux, see the Valgrind home page at
   30 
   31 	http://www.valgrind.org/
   32 
   33 Valgrind can also find memory leaks, use of uninitialized memory, and more.
   34 An impressive piece of work.
   35 
   36 --
   37 
   38 3. Why don't you rewrite the whole thing in C for speed ?
   39 
   40 You are a child who hasn't yet learned 'The Unix Philosophy'.  ;^)