You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@ant.apache.org by Stefan Bodewig <bo...@apache.org> on 2002/09/11 11:50:01 UTC
Re: Crash after creation of last jar.
<http://nagoya.apache.org/bugzilla/show_bug.cgi?id=11903>
the reports seem to indicate it is a problem with IBM's JVM(s).
> java version "1.3.0"
> Java(TM) 2 Runtime Environment, Standard Edition (build 1.3.0)
> Classic VM (build 1.3.0, J2RE 1.3.0 IBM build cx130-20010626 (JIT
> enabled: jitc))
Any chance you could upgrade to 1.3.1 or disable the JIT to confirm
that either fixes the problem?
Stefan
--
To unsubscribe, e-mail: <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>
Re: Crash after creation of last jar.
Posted by Stefan Bodewig <bo...@apache.org>.
On Wed, 11 Sep 2002, Markus Bernhardt <mb...@swsgmbh.de> wrote:
> Yes, disabling the JIT fixes the problem.
Thanks.
> Upgrading to IBM 1.3.1 or Sun 1.3.0 or higher
> is not possible, because this machine has a
> 2.2.12 kernel and a really ancient glibc, so I can't
> say whether that helps.
I have some Redhat 6.1 boxes (seems as ancient as your system) that
happily run Sun's 1.3.1_3.
> Thanks again.
You're welcome
Stefan
--
To unsubscribe, e-mail: <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>
Re: Crash after creation of last jar.
Posted by Markus Bernhardt <mb...@swsgmbh.de>.
Hi,
thanks for the fast response.
Yes, disabling the JIT fixes the problem.
Upgrading to IBM 1.3.1 or Sun 1.3.0 or higher
is not possible, because this machine has a
2.2.12 kernel and a really ancient glibc, so I can't
say whether that helps.
Thanks again.
- markus
Stefan Bodewig wrote:
> <http://nagoya.apache.org/bugzilla/show_bug.cgi?id=11903>
>
> the reports seem to indicate it is a problem with IBM's JVM(s).
>
> > java version "1.3.0"
> > Java(TM) 2 Runtime Environment, Standard Edition (build 1.3.0)
> > Classic VM (build 1.3.0, J2RE 1.3.0 IBM build cx130-20010626 (JIT
> > enabled: jitc))
>
> Any chance you could upgrade to 1.3.1 or disable the JIT to confirm
> that either fixes the problem?
>
> Stefan
>
> --
> To unsubscribe, e-mail: <ma...@jakarta.apache.org>
> For additional commands, e-mail: <ma...@jakarta.apache.org>