public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: Michael S. Zick <mszick@goquest.com>
To: Alexandre Oliva <aoliva@redhat.com>, Joe Buck <jbuck@synopsys.com>
Cc: gcc@gcc.gnu.org
Subject: Re: 3.2.3-pre tarball 2: libjava build still fails on sparc-sun-solaris2.8
Date: Thu, 24 Apr 2003 16:15:00 -0000	[thread overview]
Message-ID: <03042409381200.00937@wolf686> (raw)
In-Reply-To: <ory920971o.fsf@localhost.localdomain>

On Wednesday 23 April 2003 05:34 pm, Alexandre Oliva wrote:
> On Apr 23, 2003, Joe Buck <jbuck@synopsys.com> wrote:
> > I realize that getting libtool to work right and portably is a tough job.
>
> Thanks; it is, indeed :-)
I may have stumbled on a BASH behavior that could cause erratic
script execution.  In brief...
While working on a script containing a sequence of shell commands
(internal bash commands) that caused BASH to fork multiple threads...

Getting totally unexpected behavior, in a seperate term, I attached an:
strace -fF -e trace=process -p PID_of_first_term

And found that my script was putting BASH into a state where it
was doing a "wait4" on a single child when it should have been
doing, in effect, a "wait4 ALL" of the child threads it had created.

Such a problem could be in any of:
BASH - 2.0.5, version 2.05a.0(1)-release
Perhaps in the threading:
glibc version 2.2.2
Perhaps in the scheduler behavior of the OS:
Linux-2.4.20 (2 processor, SMP )

It is a rare, but repeatable "corner case" once you have the
situation where, of the multiple threads created, at least one
of them has significantly longer execution time than the rest;
leading to "out of order" completion.

Just a "heads up" that BASH scripts may not be completing
things in the order the author has envisioned (coded).

Mike

  reply	other threads:[~2003-04-24 14:45 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-04-17 16:56 Joe Buck
2003-04-17 18:15 ` H. J. Lu
2003-04-17 22:16   ` Joe Buck
2003-04-18 16:26     ` Eric Botcazou
2003-04-18 17:18       ` Joe Buck
2003-04-18 17:25         ` Gabriel Dos Reis
2003-04-19  7:42         ` Eric Botcazou
2003-04-21 16:57           ` Joe Buck
2003-04-21  3:36       ` Gerald Pfeifer
2003-04-21 13:54         ` Gabriel Dos Reis
2003-04-23 19:03           ` Alexandre Oliva
2003-04-23 19:24             ` Joe Buck
2003-04-23 23:35               ` Alexandre Oliva
2003-04-24 16:15                 ` Michael S. Zick [this message]
2003-04-25 14:45             ` libjava build still fails on sparc-sun-solaris2.9 Gerald Pfeifer

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=03042409381200.00937@wolf686 \
    --to=mszick@goquest.com \
    --cc=aoliva@redhat.com \
    --cc=gcc@gcc.gnu.org \
    --cc=jbuck@synopsys.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).