Skip to main content

Running cldc_vm

4 replies [Last post]
chukmunnlee
Offline
Joined: 2004-01-14
Points: 0

Hi all,

I've manage to build the phoneME VM, not MIDP on Linux. This is basically for testing. I wrote a little hello world program and tested on

cldc_vm
cldc_vm_g
cldc_vm_r

The app only manage to run on cldc_vm_g. For the other 2 VMs, I got a segmentation fault. BTW, I'm using on PCSL and no Javacall. Here is the out put from cldc_vm_r

=========================================================

$ bin/cldc_vm_r =HeapCapacity2M -cp . -verbose TestTZ
Object heap [0xb7a4b000,0xb7c4b000), 2097152 bytes
total/free bytes [2097152,1677720]
- Collection area [0xb7a4b000,0xb7a4b000, 0xb7be4998)
- Compiler area [0xb7be4998,0xb7be4998, 0xb7c4b000)
- Large object area [0xb7be4998,0xb7c4b000, 0xb7c4b000)
Min marking stack [0xb7c4b000,0xb7ee7000)
Bit vector [0xb7ee7000,0xb7ef7000), 65536 bytes
Slices start 0xb7ef7000
Slice size 4096
Number of slices 128 (=512 bytes)
Task 0 usage 0
Task 1 usage 0
Task 2 usage 0
Task 3 usage 0
Task 4 usage 0
Task 5 usage 0
Task 6 usage 0
Task 7 usage 0
Task 8 usage 0
Task 9 usage 0
Task 10 usage 0
Task 11 usage 0
Task 12 usage 0
Task 13 usage 0
Task 14 usage 0
Task 15 usage 0
initial heap size = 2048K
young gen size = 1638K
young gen min (estimate) = 20K
compiler area = 409K
Fatal signal SIGSEGV: errno=0; code=1; addr=0x8
[Dumping all threads]
Current thread = 0x0

[Finished dumping all threads]

=========================================================

Pointers appreciated.

Thanks

Regards
Chuk

Reply viewing options

Select your preferred way to display the comments and click "Save settings" to activate your changes.
danila
Offline
Joined: 2006-09-25
Points: 0

What is the gcc version on your machine?

Also try to build product VM (cldc_vm) with PRODUCT_DEBUG=true.
It will build product VM with debugging information.
Check if it runs ok.

Danila

chukmunnlee
Offline
Joined: 2004-01-14
Points: 0

Thanks for answering. My version is

[102] gcc --version
gcc (GCC) 4.3.1
Copyright (C) 2008 Free Software Foundation, Inc.
This is free software; see the source for copying conditions. There is NO
warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.

I will try building it with debug info. BTW can you tell me what is the diff between the the VMs?

cldc_vm
cldc_vm_g
cldc_vm_r

Thanks

Regards
Chuk

danila
Offline
Joined: 2006-09-25
Points: 0

cldc_vm_g is a debug VM build. It includes all runtime assertions and debug info. All development command-line options are enabled. Large and slow.

cldc_vm_r is a release VM build. No debug info, few runtime assertions. All development command-line options are enabled.

cldc_vm is a product VM build. Fully optimized for performance and footprint, no debug info, no runtime assertions. Development command-line options are disabled.

It could be useful to try build with older gcc version to check if this is a compiler issue.

flaviopereira
Offline
Joined: 2008-02-18
Points: 0

Hi

Did you manage to solve this problem, I'm having a very similar issue, only diff is that none of my 3 VM's run...?