Mailing-List: contact stdcxx-dev-help@incubator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: stdcxx-dev@incubator.apache.org
Message-ID: <15440188.1179957496500.JavaMail.jira@brutus>
Date: Wed, 23 May 2007 14:58:16 -0700 (PDT)
From: "Martin Sebor (JIRA)" <jira@apache.org>
To: stdcxx-dev@incubator.apache.org
Subject: [jira] Commented: (STDCXX-426) infinite loop in exec utility
In-Reply-To: <32810164.1179956656145.JavaMail.jira@brutus>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


    [ https://issues.apache.org/jira/browse/STDCXX-426?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12498399 ] 

Martin Sebor commented on STDCXX-426:
-------------------------------------

Here some more important detail from the thread linked above:

Also, from the trace it looks like exec sent SIGHUP to the
process after the child exited (it did this with another test
even when it didn't get into a loop). That doesn't seem right
(and neither does the PID for that matter). Exec should send
the signal only when the child doesn't exit within the
allotted period of time.

...
clone(child_stack=0, flags=CLONE_CHILD_CLEARTID|CLONE_CHILD_SETTID|SIGCHLD, child_tidptr=0x2a95764730) = 16607
...
alarm(10)                               = 0
wait4(16607, [{WIFEXITED(s) && WEXITSTATUS(s) == 0}], WSTOPPED|WCONTINUED, NULL) = 16607
--- SIGCHLD (Child exited) @ 0 (0) ---
alarm(0)                                = 10
kill(4294950689, SIGHUP)                = -1 ESRCH (No such process)
... 

> infinite loop in exec utility
> -----------------------------
>
>                 Key: STDCXX-426
>                 URL: https://issues.apache.org/jira/browse/STDCXX-426
>             Project: C++ Standard Library
>          Issue Type: Bug
>          Components: Test Driver
>    Affects Versions: 4.2
>         Environment: gcc 3.4.6 on Red Hat Advanced Server 4, 12D (shared, wide, optimized, thread-safe) build
>            Reporter: Mark Brown
>         Assigned To: Andrew Black
>            Priority: Critical
>             Fix For: 4.2
>
>         Attachments: strace.run-21.cwchar.log
>
>
> Copied from http://mail-archives.apache.org/mod_mbox/incubator-stdcxx-dev/200705.mbox/%3c4654A3FF.8020907@roguewave.com%3e
> -------- Original Message --------
> Subject: infinite loop in exec
> Date: Wed, 23 May 2007 14:28:47 -0600
> From: Martin Sebor <sebor@roguewave.com>
> Reply-To: stdcxx-dev@incubator.apache.org
> Organization: Rogue Wave Software
> To: stdcxx-dev@incubator.apache.org
> I'm running into an (almost?) infinite loop when running some
> of our tests under the exec utility on Linux (in a 12D build
> with gcc 3.4.6 on Red Hat Advanced Server 4, I haven't tried
> other configurations). The initial output of strace for one
> of the tests, 21.cwchar, is in the attached file. The test
> by itself runs fine to completion and doesn't produce any
> unusual output (no NULs).
> Andrew, when you have a chance, can you take a look at it?
> If that's not going to be soon let me know if I should open
> an issue.
> Martin

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.