That's a good idea. There could be a patch at the base of the mlvm patch queue
that adds something to the version string, so people can quickly check if they
have a prototype binary. -- John
On Jul 31, 2010, at 4:08 PM, Stephen Bannasch wrote:
> It would be nice if there was some indication i
It would be nice if there was some indication in the output of: 'java -version'
to indicate that the 1.7.0 build included the
mlvm patchset.
I've updated my build scripts so that it's easy to build Java 1.7.0 and
1.7.0-mlvm.
The bash function I use to switch which Java I am using works fine bu
>Le 31/07/2010 19:56, Stephen Bannasch a écrit :
>> I'm not sure if jhat works with mlvm but I tried Charlie's first simple
>> example here:
>>
>> http://blog.headius.com/2010/07/browsing-memory-jruby-way.html
>>
>> and got the following error:
>>
>> [dev]$ jmap -histo:live 77467
>> java.lang.
Le 31/07/2010 19:56, Stephen Bannasch a écrit :
> I'm not sure if jhat works with mlvm but I tried Charlie's first simple
> example here:
>
> http://blog.headius.com/2010/07/browsing-memory-jruby-way.html
>
> and got the following error:
>
> [dev]$ jmap -histo:live 77467
> java.lang.NullPointe
I'm not sure if jhat works with mlvm but I tried Charlie's first simple example
here:
http://blog.headius.com/2010/07/browsing-memory-jruby-way.html
and got the following error:
[dev]$ jmap -histo:live 77467
java.lang.NullPointerException
at java.io.File.(File.java:293)
at
s
