This is the mail archive of the
mailing list for the Cygwin project.
"fork problem" debugging
- From: "Bryan D. Thomas" <cinder_bdt at yahoo dot com>
- To: cygwin at cygwin dot com
- Date: Wed, 17 May 2006 19:39:29 -0700 (PDT)
- Subject: "fork problem" debugging
I'm taking the risk of conflating several different
issues into one. On the other hand, this might be a
useful synthesis to help us bottom out on "fork
problems" so that we can turn a snapshot into a stable
I've been trying to figure out strace incantations.
Hopefully someone more wizardly can help? Is strace
the best/only attack vector on this?
In  Torfinn Ottesen wrote:
> I find that my loops are OK until after about 80
> cases, each loop increases my memory usage by about
> 3.2 MB
> I am aware of the following information:
> I have strace but do not know what to do with it
I wonder if some strace like  would help?
Perhaps someone could suggest a helpful "cheatsheet"
what we might want to focus on in strace output of
If it would be helpful to run strace against the
processes in the weather.sh fork example
, or in the nonsense testcase example
...what should the command line be, and what would we
be looking for in output?
In , Larry Hall wrote:
> Sounds to me like the situation you found closely
> mirrors the behavior the MS KB article describes.
> I think it's worthwhile for you to experiment
> with the workaround proposed to see if it helps.
> It would be beneficial if you reported any results
> you saw back to this list.
Torfinn, any luck on SharedSection parameter tweaking
per the MS KB?
Do You Yahoo!?
Tired of spam? Yahoo! Mail has the best spam protection around
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Problem reports: http://cygwin.com/problems.html