From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 79220 invoked by alias); 30 Mar 2016 20:16:12 -0000 Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@cygwin.com Mail-Followup-To: cygwin@cygwin.com Received: (qmail 79207 invoked by uid 89); 30 Mar 2016 20:16:12 -0000 Authentication-Results: sourceware.org; auth=none X-Virus-Found: No X-Spam-SWARE-Status: No, score=0.1 required=5.0 tests=AWL,BAYES_00,KAM_LAZY_DOMAIN_SECURITY autolearn=no version=3.3.2 spammy=H*r:ip*192.168.1.100, H*RU:!192.168.1.100!, Hx-spam-relays-external:!192.168.1.100! X-HELO: m0.truegem.net Received: from m0.truegem.net (HELO m0.truegem.net) (69.55.228.47) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with (AES256-SHA encrypted) ESMTPS; Wed, 30 Mar 2016 20:16:09 +0000 Received: (from daemon@localhost) by m0.truegem.net (8.12.11/8.12.11) id u2UKG7EY038611 for ; Wed, 30 Mar 2016 13:16:07 -0700 (PDT) (envelope-from mark@maxrnd.com) Received: from 76-217-5-154.lightspeed.irvnca.sbcglobal.net(76.217.5.154), claiming to be "[192.168.1.100]" via SMTP by m0.truegem.net, id smtpdcGgw5l; Wed Mar 30 12:16:06 2016 Subject: Re: How to profile DLL built by Cygwin To: cygwin@cygwin.com References: From: Mark Geisert Message-ID: <56FC340D.5050507@maxrnd.com> Date: Wed, 30 Mar 2016 20:16:00 -0000 User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:42.0) Gecko/20100101 Firefox/42.0 SeaMonkey/2.39 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit X-SW-Source: 2016-03/txt/msg00562.txt.bz2 John Smith wrote: > I have an executable using a DLL. The DLL is built using -g -pg. > Running the executable, however, does not produce a gmon.out. file. > Cygwin version is 1.7.33. Thanks in advance for any suggestions. Cygwin's profiling facility currently only supports one address range: the address range of the executable's .text segment. DLLs live in other address ranges. Currently the only way to profile DLL code on Cygwin is to temporarily make the DLL a static library, e.g. libfoo.a, and link it into the executable's build. HTH, ..mark -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation: http://cygwin.com/docs.html Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple