delorie.com/archives/browse.cgi | search |
Xref: | news-dnh.mv.net comp.os.msdos.djgpp:1146 |
Path: | news-dnh.mv.net!mv!news.sprintlink.net!tank.news.pipex.net!pipex!news.mathworks.com!zombie.ncsc.mil!news.duke.edu!convex!bcm!newsfeed.rice.edu!rice!news!sandmann |
From: | Charles Sandmann <sandmann AT clio DOT rice DOT edu> |
Newsgroups: | comp.os.msdos.djgpp |
Subject: | Re: How do I get GPROF to work ? |
Date: | Tue, 25 Jul 1995 09:49:49 CDT |
Organization: | Rice University, Houston, Texas |
Lines: | 12 |
References: | <3v2o2b$4gv AT ucthpx DOT uct DOT ac DOT za> |
Reply-To: | sandmann AT clio DOT rice DOT edu |
Nntp-Posting-Host: | clio.rice.edu |
To: | djgpp AT sun DOT soe DOT clarkson DOT edu |
Dj-Gateway: | from newsgroup comp.os.msdos.djgpp |
> I compiled and linked my program with the '-gp' option (I think it isn't > needed during linking, or is it?). Anyway, I then ran 'gprof program', 1) Compile with -pg. Yes, it is needed in linking! 2) Run the program, it creates a file gmon.out 3) run "gprof program". This analyzes gmon.out using info from program, displays on screen. I recommend "gprof program > program.prf" so you can analyze in detail. Profiling timing results will be 0 under DPMI with V1.x, so you probably should avoid DPMI when profiling. Timing works under V2 and will be in the next beta.
webmaster | delorie software privacy |
Copyright © 2019 by DJ Delorie | Updated Jul 2019 |