From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from m0.truegem.net (m0.truegem.net [69.55.228.47]) by sourceware.org (Postfix) with ESMTPS id 300B13951C66 for ; Mon, 19 Apr 2021 05:16:04 +0000 (GMT) DMARC-Filter: OpenDMARC Filter v1.3.2 sourceware.org 300B13951C66 Authentication-Results: sourceware.org; dmarc=none (p=none dis=none) header.from=maxrnd.com Authentication-Results: sourceware.org; spf=none smtp.mailfrom=mark@maxrnd.com Received: (from daemon@localhost) by m0.truegem.net (8.12.11/8.12.11) id 13J5G2q0012628 for ; Sun, 18 Apr 2021 22:16:02 -0700 (PDT) (envelope-from mark@maxrnd.com) Received: from 162-235-43-67.lightspeed.irvnca.sbcglobal.net(162.235.43.67), claiming to be "[192.168.1.100]" via SMTP by m0.truegem.net, id smtpdSqqoAR; Sun Apr 18 22:16:00 2021 Subject: Re: Maybe consider rpmalloc To: cygwin-developers@cygwin.com References: <067987e2-e958-b56c-efea-25d827568453@maxrnd.com> <6f68b10b-7fe5-4378-afb9-9001de084edf@maxrnd.com> <3adb36f3-8740-3ff7-5f8a-90cdf3dfb64d@maxrnd.com> <69159cfa-8fc5-283b-126b-740b841841cd@maxrnd.com> <93809c4f-7747-3611-0d20-bde09e091f1d@maxrnd.com> From: Mark Geisert Message-ID: Date: Sun, 18 Apr 2021 22:16:00 -0700 User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:52.0) Gecko/20100101 Firefox/52.0 SeaMonkey/2.49.4 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit X-Spam-Status: No, score=-3.9 required=5.0 tests=BAYES_00, KAM_DMARC_STATUS, KAM_LAZY_DOMAIN_SECURITY, NICE_REPLY_A, SPF_HELO_NONE, SPF_NONE, TXREP autolearn=no autolearn_force=no version=3.4.2 X-Spam-Checker-Version: SpamAssassin 3.4.2 (2018-09-13) on server2.sourceware.org X-BeenThere: cygwin-developers@cygwin.com X-Mailman-Version: 2.1.29 Precedence: list List-Id: Cygwin core component developers mailing list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 19 Apr 2021 05:16:10 -0000 Jon Turney wrote: > On 14/04/2021 09:19, Mark Geisert wrote: >> I need to identify what's being hit within ntdll.dll.  Is it one or two >> routines, or just hot locks.  So that means getting the correct PDB file from >> the MS Symbol Server and working with Windows tools I'm unfamiliar with.  Sigh, >> in an earlier life I had a gdb that we'd taught how to work > > Yes, this would indeed be a very useful thing to have in gdb. > > I'm not aware of any public work in that direction, though. > >> with PDB files; dunno if I could resurrect that.  Profiling the Cygwin DLL >> itself, call profiling I mean, might lead somewhere as well. > > In the past I've had some success with using the Very Sleepy profiler ([1]), which > can use both PDB and DWARF symbols, on cygwin executables. > > [1] https://github.com/VerySleepy/verysleepy Thanks for that link, Jon. That tool is potentially very useful. Are you sure it understands DWARF though? It seems to show only a subset of cygwin1.dll symbols but I can't immediately tell why those and not others. Perhaps they're just the unmangled names present in the COFF symbol table? Did you do anything in particular to assist it with debugging Cygwin exes? Like adding to the Symbol Cache it builds? I only see PDB files in its cache so far. I think building a "fake" PDB file for cygwin1.dll might be good enough, but if there's an easier way I'd love to hear it. Thanks again, ..mark