Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , 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: <002001c30f60$523ccfe0$24784e51@ellixia> From: "Elfyn McBratney" To: "cygwin" References: <01c701c30f5b$1e283d20$9aea86d9 AT ellixia> Subject: Re: App w/excessive soft page faults Date: Wed, 30 Apr 2003 22:07:14 +0100 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106 > > I have an app that is generating excessive soft page faults 500-700+/sec. > > pfmon shows they happen here: > > > > SOFT: RtlTimeFieldsToTime+0x3dd : 0a7cb004 > > SOFT: stricmp+0x2f6 : 0a7da3ac > > > > This pattern repeats endlessly. > > > > We probably do make a lot of time related calls, but is this page faulting > > behavior "normal"? Any idea of how to track this back through cygwin1.dll > > and into my app? Thanks. > > First you need to compile your application with debugging symbols (the '-g' > flag to gcc/c++). Once you've done that you can start your program under gdb > like so > > $ gdb /path/to/app.exe > (gdb) run [put any args here] > > and you can then issue the 'bt' command to gdb to get the backtrace, or if > you suspect the problem is occurring inside the (Cygwin) DLL you can do > > (gdb) dll cygwin1 > (gdb) thread 1 > (gdb) bt > > this... I may have some of the above wrong (?). Having just re-read that, if your program functions and doesn't SIGSEGV then it it won't be stack dumping, will it? Elfyn -- 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/