Bug#238432: gcj-3.3: gcj fails to wait for its child processes on exec()

[Jari Juslin <zds@iki.fi>]

Package: gcj-3.3
Version: 1:3.3.3-3
Severity: normal
Tags: sid

When calling Runtime.getRuntime.exec(String) in program that has been
compiled with gcj-3.3.3, process is created and works as expected, but
process is not reaped. With Sun JVM 1.5.0-beta the same programs work
fine.

We tested this also with gcc-snapshot 20040314-1, with same results.

Steps to reproduce:
1) Write a program that calls Runtime.getRuntime.exec("uptime"),
opens and closes both input and output stream and calls destroy()
to process (or use the one I attach when this report hits the web)
and that continues to run.
2) See process listing: the processes created by exec() show there
as <defunct>.

-- System Information: Debian Release: testing/unstable
  APT prefers unstable
  APT policy: (500, 'unstable')
Architecture: i386 (i686)
Kernel: Linux 2.6.3-1-k7
Locale: LANG=fi_FI.ISO-8859-15@euro, LC_CTYPE=fi_FI.ISO-8859-15@euro

Versions of packages gcj-3.3 depends on:
ii  g++-3.3                     1:3.3.3-3    The GNU C++ compiler
ii  gcc-3.3-base                1:3.3.3-3    The GNU Compiler Collection (base 
ii  java-common                 0.22         Base of all Java packages
ii  libc6                       2.3.2.ds1-11 GNU C Library: Shared libraries an
ii  libgcc1                     1:3.3.3-3    GCC support library
ii  libgcj4                     1:3.3.3-3    Java runtime library for use with 
ii  zlib1g                      1:1.2.1-5    compression library - runtime

-- no debconf information