Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Subscribe: <mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive: <http://sources.redhat.com/ml/cygwin/>
List-Post: <mailto:cygwin AT cygwin DOT com>
List-Help: <mailto:cygwin-help AT cygwin DOT com>, <http://sources.redhat.com/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
X-Authentication-Warning: slinky.cs.nyu.edu: pechtcha owned process doing -bs
Date: Wed, 30 Apr 2003 17:12:45 -0400 (EDT)
From: Igor Pechtchanski <pechtcha AT cs DOT nyu DOT edu>
Reply-To: cygwin AT cygwin DOT com
To: Brian Ford <ford AT vss DOT fsi DOT com>
cc: cygwin <cygwin AT cygwin DOT com>
Subject: Re: App w/excessive soft page faults
In-Reply-To: <Pine.GSO.4.44.0304301601010.18331-100000@eos>
Message-ID: <Pine.GSO.4.44.0304301711060.25128-100000@slinky.cs.nyu.edu>
Importance: Normal
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII

On Wed, 30 Apr 2003, Brian Ford wrote:

> I tried setting a break point on RtlTimeFieldsToTime and
> RtlTimeFieldsToTime+0x3dd.  They never triggered.
>
> Do breakpoints in dlls work?

Yes, they do.

You might try getting a debug version of cygwin1.dll with sources and
setting a breakpoint in stricmp (which is part of newlib, I believe)...
	Igor

> On Wed, 30 Apr 2003, Elfyn McBratney wrote:
>
> > > 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 (?).
> > Elfyn

-- 
				http://cs.nyu.edu/~pechtcha/
      |\      _,,,---,,_		pechtcha AT cs DOT nyu DOT edu
ZZZzz /,`.-'`'    -.  ;-;;,_		igor AT watson DOT ibm DOT com
     |,4-  ) )-,_. ,\ (  `'-'		Igor Pechtchanski
    '---''(_/--'  `-'\_) fL	a.k.a JaguaR-R-R-r-r-r-.-.-.  Meow!

Knowledge is an unending adventure at the edge of uncertainty.
  -- Leto II


--
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/