Re: [Midpath-general] Midpath on ARM9, using Jamvm ives Segmentaion fault

[Guillaume L. <gl...@th...>]

2007/8/10, Subbu Linux <sub...@gm...>:
> Hello Team,
> I am curently using midpath-0.1-alpha2, jamvm-1.4.5 and classpath-0.93 for
> ARM Target.
> I was able to cross compile Jamvm and Classpath for ARM target, to say
> specfically LN2410 SOC, I was able to run console programs say
> Helloworld.java using Jamvm,
> but when I tried running midpath-test.sh with Jamvm, I am getting
> Segmentation problem after Loading ..../events/Native.class just before
> Creating Native class array.
> I request someone to throw pointers on it.
>
> I have other quetsion, do Midpath depends on size of Ram? currently I have
> 64MB on my board.
>
> And question with respect to casspath, what is the dependecy of midpath on
> Classpath compilied --diable-gtk-peer, --diable-gconf-peer and without
> plugins support?
>
> Hope someone can give me poiners or even some refernce to read about may
> help me to solve problem.
>
> Regards
> Subbu
>

Hi Subbu,

> but when I tried running midpath-test.sh with Jamvm, I am getting
> Segmentation problem after Loading ..../events/Native.class just before
> Creating Native class array.

Could you provide more traces ?

> I have other quetsion, do Midpath depends on size of Ram? currently I have
> 64MB on my board.

MIDPath doesn't use a lot of memory. Hence 64 MB should be sufficient by far.

> And question with respect to casspath, what is the dependecy of midpath on
> Classpath compilied --diable-gtk-peer, --diable-gconf-peer and without
> plugins support?

MIDPath uses only a few packages from Classpath : java.lang, java.io,
java.net, java.util. It doesn't rely on Classpath's AWT peers (except
if you use the MIDPath's AWT backend) nor plugin support.

Regards,
Guillaume

PS: Feel free to join #thenesis IRC channel on irc.freenode.net and
ask any questions