Christopher,
I haven't seen the entire discussion on the stackdumps occurring in
recursive makes but wanted to share a piece of information with those
interested in the topic. I've been encountering the problem for months and
have been using the same solution as apparently a lot of others, running
the target twice. Like others, I am seeing the problem in rlogin or rsh
sessions as opposed to bash shells opened directly on the machines.
For speed, I recently added a dual Pentium-4 system (Dell Workstation 530)
to my collection of build servers. Builds on this new system generate one
or two errors per week whereas I get one to two dozen errors per build on
my Pentium-3 systems.
This leads me to wonder if the issues is related to system speed, timing,
or maybe the network hardware/driver of the machines. Hope this helps.
Hayden Ridenour
At 01:38 PM 9/14/2001 -0400, Christopher Faylor wrote:
>On Fri, Sep 14, 2001 at 06:38:30PM +0200, Gerrit P. Haase wrote:
> >make[3]: Leaving directory
> `/perl/stuff/sound/lilybuild/lilypond-1.4.7/input/bugs'
> > 0 [main] make 125 open_stackdumpfile: Dumping stack trace to
> make.exe.stackdump
> >Signal 11
> >
> >It is the second time I get a stackdump from make.
> >
> >What can cause this, besides a bug somewhere?
>
>Did you actually read the 1.3.3 release announcement?
>
>cgf
>
>--
>Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
>Bug reporting: http://cygwin.com/bugs.html
>Documentation: http://cygwin.com/docs.html
>FAQ: http://cygwin.com/faq/
--
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Bug reporting: http://cygwin.com/bugs.html
Documentation: http://cygwin.com/docs.html
FAQ: http://cygwin.com/faq/
