Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Subscribe: <mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive: <http://sourceware.org/ml/cygwin/>
List-Post: <mailto:cygwin AT cygwin DOT com>
List-Help: <mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/ml/#faqs>
Sender: cygwin-owner AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
Delivered-To: mailing list cygwin AT cygwin DOT com
Message-ID: <9e9109705082610152a21d62b@mail.gmail.com>
Date: Fri, 26 Aug 2005 10:15:25 -0700
From: Amos Anderson <nitroamos AT gmail DOT com>
Reply-To: amosa AT caltech DOT edu
To: cygwin AT cygwin DOT com
Subject: base relocations and vtune
Mime-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Disposition: inline
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by delorie.com id j7QHFbnQ016322

hello -- i'm trying to figure out how to profile my code compiled with
gcc/cygwin with intel vtune's call graph.

this might be a problem specific to the call graph functionality itself.

i was able to instrument all my program with vtune so i can run the
call graph activity, but i get the warning "Module does not contain
base relocations." a popup message informs me about the /fixed:no
change for use with visual studio -- but i've been unable to find an
analogous makefile modification for gcc/cygwin.

when i run the call graph activity on my executables, it runs just
fine, but none of my functions show up in the call list. only system
dll functions show up -- and the graph attempts to build a tree out of
cygwin1.dll, kernel32.dll, et al.

by searching i found the "GCC for Windows help" thread, which seems to
touch on this issue
http://sourceware.org/ml/cygwin/2003-05/msg00436.html
but i don't understand what they're talking about (i don't know what
"base relocations" themselves are...)

i would appreciate any guidance on this topic.

thanks!

amos.

--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Problem reports:       http://cygwin.com/problems.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/