<ARM> NaCl module doesn't load on Chrome

[siba samal]

After adding a small patch to nacl.gyp file I am able to build
chromium with NaCl.

But it fails while downloading/verifying the module.
[Command] ./chrome --enable-nacl http://[IP:5103]/scons-out/nacl-arm/staging/examples.html

[Error Log]

[6126,1074013024:08:30:00.401804] Looking at segment 4, type 0x7,
p_flags 0x4
[6126,1074013024:08:30:00.402018] Matched nacl_phdr_check_data[4]
[6126,1074013024:08:30:00.402229] Ignoring
[6126,1074013024:08:30:00.402439] rodata_end = 00050320
[6126,1074013024:08:30:00.402649] data_start = 00060000
[6126,1074013024:08:30:00.402858] data_end = 000618c0
[6126,1074013024:08:30:00.403069] max_vaddr = 000618c0
[6126,1074013024:08:30:00.403278] static_text_end: 0x000000000003bd40
break_add: 0x00000000000618c0 data_end: 0x00000000000618c0 entry_pt:
0x0000000000020020 bundle_size: 0x10
[6126,1074013024:08:30:00.403496] Allocating address space
[6126,1074013024:08:30:00.403722] NaClAllocAddrSpace: calling
NaClAllocateSpace(*,0x0000000040000000)
[6116,1092584640:08:30:01.910811] only received 0 (0x0) bytes, but
internal header is 16 (0x10) bytes
[6116,1092584640:08:30:01.911298] NaClImcRecvTypedMsg: returning -5
failed to send nexe
[6116,1092584640:08:30:01.914340] NaClRefCountSafeUnref(0x02487808).
[6116,1092584640:08:30:01.914857] NaClRefCountUnref(0x02487808).
Load: Failed to start service runtime
[6116,1092584640:08:30:01.916041] NaClRefCountUnref(0x02487808).



Could anyone help me ?????????? Thnx in advance :)

[Mark Seaborn]

On 3 November 2010 13:54, siba samal <siba...@gmail.com> wrote:

After adding a small patch to nacl.gyp file I am able to build
chromium with NaCl.

But it fails while downloading/verifying the module.
[Command] ./chrome --enable-nacl http://[IP:5103]/scons-out/nacl-arm/staging/examples.html

Yes, NaCl does not work when built into Chromium on ARM yet.  This is because the ARM sandbox needs to reserve the bottom 1Gb of address space, and this is not yet implemented for the Chromium integration.  See http://code.google.com/p/nativeclient/issues/detail?id=303

Cheers,
Mark