This is the mail archive of the
cygwin-developers@cygwin.com
mailing list for the Cygwin project.
Re: possible mmap() problems
- From: Matt <matt at use dot net>
- To: Joe Buehler <jbuehler at hekimian dot com>
- Cc: <cygwin-developers at cygwin dot com>
- Date: Wed, 16 Apr 2003 13:19:40 -0700 (PDT)
- Subject: Re: possible mmap() problems
On Wed, 16 Apr 2003, Joe Buehler wrote:
> Christopher Faylor wrote:
>
> > If it's predictable where the page is, then I wonder if you could set a
> > hardware watchpoint to catch when it is happening? Or maybe even strace
> > would tell you.
>
> It's a hard one. I have a build that fails randomly. On one run,
> out of 51 errors (handle_exceptions) caught by strace, 49 of them
> happened right after a pipe close. I believe that they all did happen
> at the same address. Adding strace printfs for Virtual* calls caused
> the problem to (apparently) go away (sigh).
>
> I assume I can't use hardware watchpoints because there are lots and lots
> of processes coming and going while the build is going on, and no apparent
> rhyme or reason to the problem.
Sounds like a job for Softice or windbg.. windbg can be gotten for free @
www.microsoft.com/ddk . I'm more familiar with Softice, but I've seen
othre people use windbg to set a hardware breakpoint on a memory location.
--
http://www.clock.org/~matt