home *** CD-ROM | disk | FTP | other *** search
/ NetNews Usenet Archive 1993 #3 / NN_1993_3.iso / spool / comp / sys / sgi / 19162 < prev    next >
Encoding:
Text File  |  1993-01-28  |  1.5 KB  |  31 lines
  1. Newsgroups: comp.sys.sgi
  2. Path: sparky!uunet!UB.com!pacbell.com!decwrl!spool.mu.edu!yale.edu!qt.cs.utexas.edu!cs.utexas.edu!sdd.hp.com!saimiri.primate.wisc.edu!ames!nsisrv!climate!merritt
  3. From: merritt@climate.NoSubdomain.NoDomain (John H. Merritt)
  4. Subject: Re: How to know how much memory needed to run executable(a.out)
  5. Message-ID: <1993Jan26.221254.14768@nsisrv.gsfc.nasa.gov>
  6. Sender: usenet@nsisrv.gsfc.nasa.gov (Usenet)
  7. Nntp-Posting-Host: climate.gsfc.nasa.gov
  8. Organization: Climate and Radiation Branch
  9. References:  <C19tKx.F0u@news.cso.uiuc.edu>
  10. Date: Tue, 26 Jan 1993 22:12:54 GMT
  11. Lines: 18
  12.  
  13. In article <C19tKx.F0u@news.cso.uiuc.edu>, amg8408@uxa.cso.uiuc.edu (Avijit  Moitra) writes:
  14. |> I am interested to know how much memory (core) will be needed to run
  15. |> my executable.  It does not run on a 16MB m/c but runs on a 32-64 MB
  16. Run the program on the 32-64MB machine.
  17. Identify the process with ps.
  18. ls -l /debug | grep pid     --     where pid is the process id that
  19.                                    you found with ps.  The size field
  20.                                    of ls is the core size of your program.
  21.  
  22. -- 
  23.         \___   \______   \__  \__  \___   \__
  24.         \___  \________  \__  \__  \____  \__
  25.         \___  \__   \__  \__  \__  \_____ \__
  26.         \___  \__   \__  \_______  \__ \__\__   merritt@climate.gsfc.nasa.gov
  27. \___    \___  \__   \__  \_______  \__  \____   
  28. \___    \___  \__   \__  \__  \__  \__   \___   "Yesterday I knew nothing,
  29.  \_________   \_______   \__  \__  \__    \__    Today I know that."
  30.   \______      \_____    \__  \__  \__     \_
  31.