Mailing-List:	contact cygwin-developers-help AT cygwin DOT com; run by ezmlm
List-Subscribe:	<mailto:cygwin-developers-subscribe AT cygwin DOT com>
List-Archive:	<http://sources.redhat.com/ml/cygwin-developers/>
List-Post:	<mailto:cygwin-developers AT cygwin DOT com>
List-Help:	<mailto:cygwin-developers-help AT cygwin DOT com>, <http://sources.redhat.com/ml/#faqs>
Sender:	cygwin-developers-owner AT cygwin DOT com
Delivered-To:	mailing list cygwin-developers AT cygwin DOT com
MIME-Version:	1.0
Subject:	profiling conundrum
X-MimeOLE:	Produced By Microsoft Exchange V6.0.5762.3
content-class:	urn:content-classes:message
Date:	Fri, 24 May 2002 23:48:44 +1000
Message-ID:	<FC169E059D1A0442A04C40F86D9BA7600C615D@itdomain003.itdomain.net.au>
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
From:	"Robert Collins" <robert DOT collins AT itdomain DOT com DOT au>
To:	<cygwin-developers AT cygwin DOT com>
X-MIME-Autoconverted:	from quoted-printable to 8bit by delorie.com id g4OE4Qq07308

Ok, the profiling patch I sent is somewhat wrong - the gcrt0.o should
not be linked with cygwin1.dll. However: this call
monstartup ((u_long) &eprol, (u_long) &etext);
is wrong. 

The result being that the gmon data fields
p->lowpc
p->highpc
p->textsize 

are wrong, and the in-cygwin calls to mcount() return without logging
the call arc because of the test for frompc >  p->textsize.

So, if anyone has some idea, on how the gcrt0.o code can be tweaked such
that the monstartup call is given the real low and high limits for the
object, that'd be great.

Rob

- Raw text -