From: James Gunning <James.Gunning@csiro.au>
To: yellowdog-general@lists.terrasoftsolutions.com,
linuxppc-dev@lists.linuxppc.org
Subject: IBM jdk needs kernel patch to fix floating stacks problem? LD_ASSUME_KERNEL
Date: Thu, 16 May 2002 10:07:48 +1000 [thread overview]
Message-ID: <3CE2F854.1020908@csiro.au> (raw)
In-Reply-To: 20020515212704.714BF1FC2D@newhope.terraplex.com
Hi ppc'ers
From discussion on the ibm.software.java.linux newsgroup
---snipped-- below, it's clear
we ppc users need some kernel patch to get the IBM jdk's (1.3.0, 1.3.1)
to work.
Anybody got any ideas if this is possible? Where to get the patch? Is
there a patch?
Any views welcome,
James.
-----snipped from ibm.software.java.linux -----
> Hi all,
>
> When trying to use the pSeries JDK with Tomcat v4.0.3, it bombs out on
> startup like so:
>
> **Out of memory, aborting**
>
> *** panic: JVMST058: Cannot allocate memory in initGcHelpers(3)
>
> It then leaves a 60MB or so core file, and exits.
>
> I have tried all sorts of combinations of -X options to do with memory,
> none of them make any difference.
>
> The target platform is LinuxPPC v2.4.19-pre7 (v2.4.18 has same problem)
> under YDL v2.2, with glibc 2.2.5-0.19a.
>
> Anyone shed any clue? Is anyone from IBM interested in the core dump so
> it can be debugged?
>
> Regards,
> Graham
As I have just posted on another thread:
It looks very much like the floating stack thing. If YellowDog don't
give you the LD_ASSUME_KERNEL patch, then you can compile
glibc with floating stacks disabled. This course of action is only open
to the brave and the foolish.
Neil
-----snipped from ibm.software.java.linux -----
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
parent reply other threads:[~2002-05-16 0:07 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <20020515212704.714BF1FC2D@newhope.terraplex.com>]
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=3CE2F854.1020908@csiro.au \
--to=james.gunning@csiro.au \
--cc=linuxppc-dev@lists.linuxppc.org \
--cc=yellowdog-general@lists.terrasoftsolutions.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 NNTP newsgroup(s).