From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <java-prs-return-6704-listarch-java-prs=gcc.gnu.org@gcc.gnu.org>
Received: (qmail 11075 invoked by alias); 7 Sep 2005 13:13:47 -0000
Mailing-List: contact java-prs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Subscribe: <mailto:java-prs-subscribe@gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/java-prs/>
List-Post: <mailto:java-prs@gcc.gnu.org>
List-Help: <mailto:java-prs-help@gcc.gnu.org>, <http://gcc.gnu.org/ml/#faqs>
Sender: java-prs-owner@gcc.gnu.org
Received: (qmail 10966 invoked by uid 48); 7 Sep 2005 13:13:38 -0000
Date: Wed, 07 Sep 2005 13:13:00 -0000
From: "aeby at graeff dot com" <gcc-bugzilla@gcc.gnu.org>
To: java-prs@gcc.gnu.org
Message-ID: <20050907131331.23763.aeby@graeff.com>
Reply-To: gcc-bugzilla@gcc.gnu.org
Subject: [Bug libgcj/23763] New: Runtime.getRuntime().exec() signalling
X-Bugzilla-Reason: CC
X-SW-Source: 2005-q3/txt/msg00555.txt.bz2
List-Id: <java-prs.sourceware.org>

Showcase: compile exectest.c, run test.java calling 'exectest'

Runtime.exec() seems to pass down some strange signal configuration to child
processes in GCC >=4.0.0. When run from test.java the exectest.c parent process
does never get CHLD signals - they seem to get blocked (as I've seen the
rtsig-queue growing each time test.java was run).

GCC 3.3.3 does not have this problem.

-- 
           Summary: Runtime.getRuntime().exec() signalling
           Product: gcc
           Version: 4.0.1
            Status: UNCONFIRMED
          Severity: normal
          Priority: P2
         Component: libgcj
        AssignedTo: unassigned at gcc dot gnu dot org
        ReportedBy: aeby at graeff dot com
                CC: gcc-bugs at gcc dot gnu dot org,java-prs at gcc dot gnu
                    dot org
 GCC build triplet: i686-pc-linux-gnu
  GCC host triplet: i686-pc-linux-gnu
GCC target triplet: i686-pc-linux-gnu


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=23763