public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Mumit Khan <khan@xraylith.wisc.EDU>
To: "Ahrens, Frank 6537 EPE-24" <Frank.Ahrens@de.heidelberg.com>
Cc: "'cygwin@sourceware.cygnus.com'" <cygwin@sourceware.cygnus.com>
Subject: Re: How to use gprof under cygwin?
Date: Tue, 31 Aug 1999 23:49:00 -0000	[thread overview]
Message-ID: <199908041745.MAA04979@mercury.xraylith.wisc.edu> (raw)
Message-ID: <19990831234900.mitWpdnITb1F7SyHBQSay9Exd63p_ZVjameeMhY-ZCE@z> (raw)
In-Reply-To: <7B9327EED0AAD211B0750090270F68EC0BAA53@hdhexmbx02.ger02.heidelberg.com>

"Ahrens, Frank 6537 EPE-24" <Frank.Ahrens@de.heidelberg.com> writes:
> Hi,
> who can give me a hint, how to use gprof under cygwin?
> Does it generally work? Are there special things to make regarding cygwin?
> 

I have gprof for Cygwin at:
  
  ftp://ftp.xraylith.wisc.edu/pub/khan/gnu-win32/cygwin/ports/

You do as you normally would:
  
  $ gcc -pg -c foo.c
  $ gcc -pg -o foo foo.o
  $ ./foo
  $ gprof foo.exe

There are some limitations, but overall it works for C. There're problems
with C++ code (you'll probably get linker errors from multiple template
instances and so on), and you have to play a small trick with g77.

Regards,
Mumit


--
Want to unsubscribe from this list?
Send a message to cygwin-unsubscribe@sourceware.cygnus.com

  reply	other threads:[~1999-08-31 23:49 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1999-08-03 23:53 Ahrens, Frank 6537 EPE-24
1999-08-04 11:55 ` Mumit Khan [this message]
1999-08-04 12:57   ` ¨Marcel Cox
1999-08-04 13:07     ` Mumit Khan
1999-08-31 23:49       ` Mumit Khan
1999-08-31 23:49     ` ¨Marcel Cox
1999-08-31 23:49   ` Mumit Khan
1999-08-31 23:49 ` Ahrens, Frank 6537 EPE-24

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=199908041745.MAA04979@mercury.xraylith.wisc.edu \
    --to=khan@xraylith.wisc.edu \
    --cc=Frank.Ahrens@de.heidelberg.com \
    --cc=cygwin@sourceware.cygnus.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).