From: Gabriel Tanase <gabrieltanase@gmail.com>
To: gcc-help@gcc.gnu.org
Subject: gmon.out
Date: Thu, 09 Sep 2004 23:54:00 -0000 [thread overview]
Message-ID: <56c62a890409091654547ce5fb@mail.gmail.com> (raw)
Howdy,
I've been searching for a while with google to see if a similar topic
was discussed but I didn't find a good explanation. Here is my
problem. I would like when using the gprof( -pg option on the compile
line) to be able to dump the info generated into a file that has the
PID embedded somewhere in the name(something like gmon.out.2222 where
2222 is the process id for the program I am profiling). It is
particularly usefull when profiling MPI programs and you would like to
have individual traces for individual processes.
It is a fairly easy fix but I am wondering if there is a philosophical
issue that doesn't allow this to be included in the main branch of
gcc.
Most of the profile tools I know(valgrind, profile tools on IRIX)
attach the PID to the trace...
Thanks,
Gabi
reply other threads:[~2004-09-09 23:54 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=56c62a890409091654547ce5fb@mail.gmail.com \
--to=gabrieltanase@gmail.com \
--cc=gabrielt@cs.tamu.edu \
--cc=gcc-help@gcc.gnu.org \
/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).