jrate-devel Mailing List for jRate

Hello Mohamed,

On May 14, 2009, at 3:32 PM, Mohamed ALRahmawy wrote:

> Hi
>
> I just need to know how and in which file(s) exactly does the jrate
> allocates the static objects in immortal memory, i.e. how jrate
> differentiate between allocating objects referenced by the static
> variable and objects referenced by instance variables.
>
>
> e.g.
>
> class xx
> {
> static cls ref1;
> cls ref2;
>   public void sommethod()
> {
> ref1=new cls(...);//in immortal
> ref2=new cls(...);//in current memory area context of the current  
> thread
> }
>
> }
>

The example you are showing above does not necessarily shows  
allocation into immortal memory as the object you are creating will be  
allocated on the memory in which the calling thread is executing.

Now, if you refer to the run-time checks that are needed in order to  
ensure the referential integrity then that is a direct extension of  
the GCC front-end + GCC runtime for Java. I can't recall the exact  
name, but I believe it should be something like Jv_write_barrier(). In  
any case if you search this in the jRate patches you should easily  
find it.


HTH.

Cheers,
	Angelo

>
> cheers
> Mohammed
> -- 
> Mohammed Fathi ALRahmawy
> PhD Research Student
> Realtime Research Group
> University of York
>
> ------------------------------------------------------------------------------
> Crystal Reports - New Free Runtime and 30 Day Trial
> Check out the new simplified licensing option that enables
> unlimited royalty-free distribution of the report engine
> for externally facing server and web deployment.
> http://p.sf.net/sfu/businessobjects
> _______________________________________________
> jrate-devel mailing list
> jra...@li...
> https://lists.sourceforge.net/lists/listinfo/jrate-devel

Hi

I just need to know how and in which file(s) exactly does the jrate
allocates the static objects in immortal memory, i.e. how jrate
differentiate between allocating objects referenced by the static
variable and objects referenced by instance variables.

e.g.

class xx
{
static cls ref1;
cls ref2;
   public void sommethod()
{
ref1=new cls(...);//in immortal
ref2=new cls(...);//in current memory area context of the current thread
}

}


cheers
Mohammed
-- 
Mohammed Fathi ALRahmawy
PhD Research Student
Realtime Research Group
University of York

Hi Angelo and Abdul,

Right, we never did any work on 64-bit.  However, I think I've since
tried jRate on amd64 without serious difficulty (at least of this
sort).  Still, with the kind of hardware-specific tricks we play for
embedded ia32 and ppc, I'm not surprised if we'd have to reengineer a
few things for amd64.

If the need for multilib was detected when jRate was configured, you
have 32-bit jRate libraries.  You can then try compiling
HelloWorld.java with "jRate-gcj -m32 ..." and see if that solves the
segfault problem.  Otherwise, I can recommend recompiling all of jRate
binaries and libraries for 32-bit (with CFLAGS=-m32 at jRate configure
time) and seeing if that works.

Morgan

On Mon, May 11, 2009 at 12:14 PM, Angelo Corsaro
<ang...@gm...> wrote:
> Hello Abdul,
>
>        I see you are running on a 64-bit platforms and I believe that it is
> not supported. Morgan, was any work done at WashU on 64 bit?
>
> Cheers,
>        Angelo
>
> On May 10, 2009, at 11:11 PM, Abdul Haseeb Malik wrote:
>
>> Hi,
>>
>> jRate-0.7.2-3.3.3 is installed but it gives a segmentation error in all
>> programs.It is running on x86_64(AMD Opteron which has 4x4=16 cores).
>>
>>
>> /(gdb) r
>> Starting program:
>>
>> /home/haseeb/dev/jrate/jrate-0.3.7-5/jrate-0.3.7.2-3.3.3/demos/HelloWorld/a.out
>>
>> [Thread debugging using libthread_db enabled]
>>
>> Program received signal SIGSEGV, Segmentation fault.
>> 0x00007ffff75c11d9 in _Jv_RegisterClassHookDefault
>> (klass=0x7ffff7a98020) at
>>
>> /home/haseeb/dev/jrate/jrate-0.3.7-5/jrate-0.3.7.2-3.3.3/gcc/libjava/java/lang/natClassLoader.cc:357
>> 357       jint hash = HASH_UTF (klass->name);
>> Current language:  auto; currently c++
>> (gdb) display klass->name
>> 1: klass->name = (_Jv_Utf8Const *) 0x11
>> /
>>
>> Cheers
>>
>> Haseeb
>>
>>
>> ------------------------------------------------------------------------------
>> The NEW KODAK i700 Series Scanners deliver under ANY circumstances! Your
>> production scanning environment may not be a perfect world - but thanks to
>> Kodak, there's a perfect scanner to get the job done! With the NEW KODAK
>> i700
>> Series Scanner you'll get full speed at 300 dpi even with all image
>> processing features enabled. http://p.sf.net/sfu/kodak-com
>> _______________________________________________
>> jrate-devel mailing list
>> jra...@li...
>> https://lists.sourceforge.net/lists/listinfo/jrate-devel
>
>



-- 
Morgan Deters
md...@gm...

Hi,

jRate-0.7.2-3.3.3 is installed but it gives a segmentation error in all 
programs.It is running on x86_64(AMD Opteron which has 4x4=16 cores).


/(gdb) r
Starting program: 
/home/haseeb/dev/jrate/jrate-0.3.7-5/jrate-0.3.7.2-3.3.3/demos/HelloWorld/a.out 

[Thread debugging using libthread_db enabled]

Program received signal SIGSEGV, Segmentation fault.
0x00007ffff75c11d9 in _Jv_RegisterClassHookDefault 
(klass=0x7ffff7a98020) at 
/home/haseeb/dev/jrate/jrate-0.3.7-5/jrate-0.3.7.2-3.3.3/gcc/libjava/java/lang/natClassLoader.cc:357
357       jint hash = HASH_UTF (klass->name);
Current language:  auto; currently c++
(gdb) display klass->name
1: klass->name = (_Jv_Utf8Const *) 0x11
/ 

Cheers

Haseeb