Re: Java memory

Article View: comp.lang.java.advocacy

Article #149

Back to comp.lang.java.advocacy Previous Next

#149

From: Joe Seigh
Date: Fri, 23 Feb 2001 15:03

30 lines
3028 bytes

Jordi Guitart wrote:
> 
> I'm only modifying a little part of the JVM (in fact, I'm not "modifying"
> anything, I'm only replacing threads library with another one, and
> unfortunately I have lateral memory problems, so I'm trying to discover
> why?)
> 
> JGF

That's probably not a good idea as you've found out.  Java has rather
specific semantics.  The various thread libraries have slightly different
semantics, even if they're POSIX pthreads.  There's a number of places you
could have problems.  One or more of the following could apply.

1. The jvm implementor's don't understand java/jvm semantics correctly.
2. The jvm implementor's did not implement java/jvm semantics correctly.
3. The two thread libraries have different semantics and so they're not
   really interchangeable.
4. The jvm implementor's are relying on implementation side effects of
   the first library that aren't in the second library. e.g. the
   first library has FIFO locks and the second does not.  Another way
   of saying this is they're relying on undocumented behavior in
   the threads library version they are using.

So there's a lot of possibilities here, very subtle ones.  Are you
sure you want to get into this?

Joe Seigh

Joe Seigh

Technical Details

Message-ID: <3A967BA3.C506833B@genuity.com>

Path:

arc1-ca.pugleaf.net!supernews.google.com!sn-xit-02!supernews.com!easynews!feedwest.us.telia.net!us.telia.net!paloalto-snh1.gtei.net!news.gtei.net!paloalto-snr1.gtei.net.POSTED!not-for-mail

References:

<96trij$4ns$1@defalla.upc.es> <3A93B440.F8232537@evtechnology.com> <970ehj$337$1@defalla.upc.es> <3A93C9D3.6060706@evtechnology.com> <970j55$6af$1@defalla.upc.es>

Show Full Headers

Complete Article Headers

X-Google-Language: ENGLISH,ASCII-7-bit
X-Google-Thread: 10568c,3df73e04f851a6c7
X-Google-Attributes: gid10568c,public
X-Google-Thread: 10bb9b,3df73e04f851a6c7
X-Google-Attributes: gid10bb9b,public
X-Google-Thread: 1116f3,3df73e04f851a6c7
X-Google-Attributes: gid1116f3,public
X-Google-Thread: fdb77,3df73e04f851a6c7
X-Google-Attributes: gidfdb77,public
X-Google-Thread: 113ae9,3df73e04f851a6c7
X-Google-Attributes: gid113ae9,public
X-Google-Thread: 10a146,3df73e04f851a6c7
X-Google-Attributes: gid10a146,public
X-Google-ArrivalTime: 2001-02-23 07:03:18 PST
Path: arc1-ca.pugleaf.net!supernews.google.com!sn-xit-02!supernews.com!easynews!feedwest.us.telia.net!us.telia.net!paloalto-snh1.gtei.net!news.gtei.net!paloalto-snr1.gtei.net.POSTED!not-for-mail
Message-ID: <3A967BA3.C506833B@genuity.com>
From: Joe Seigh <jseigh@genuity.com>
X-Mailer: Mozilla 4.07 [en] (WinNT; I)
MIME-Version: 1.0
Newsgroups: comp.lang.java.advocacy,comp.lang.java.help,comp.lang.java.machine,comp.lang.java.programmer,de.comp.lang.java,es.comp.lenguajes.java
Subject: Re: Java memory
References: <96trij$4ns$1@defalla.upc.es> <3A93B440.F8232537@evtechnology.com> <970ehj$337$1@defalla.upc.es> <3A93C9D3.6060706@evtechnology.com> <970j55$6af$1@defalla.upc.es>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Lines: 30
X-Trace: /ba9QYd2R5/lAnKX4iY1RER/W8g0M3AvisL4bGCtX3gL43KLvToI5V5LST+p0fFLzS1IJelnJk7h!7deAs5RSWCtWpOzibXvefqyj3CjzunFKnno/0MtB1pgnhU/v7WAz1AC1ad4TCmIFmZGb+14=
X-Complaints-To: abuse@gte.net
X-Abuse-Info: Please be sure to forward a copy of ALL headers
X-Abuse-Info: Otherwise we will be unable to process your complaint properly
NNTP-Posting-Date: Fri, 23 Feb 2001 15:03:05 GMT
Distribution: world
Date: Fri, 23 Feb 2001 15:03:05 GMT

Reply to Parent Message