You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Apr 22, 2023. It is now read-only.
While I can use the data file that is supplied with the ICU source distribution I cannot get anything from the data customizer tool to work properly - it triggers a memory fault/core dump when I point node at it with the --icu-data-dir parameter and try to use the APIs (for example with the btest402.js mentioned in the wiki)
It's the same failure I get when I point the --icu-data-dir at an empty directory for which there's already an outstanding issue (https://github.com/srl295/node/issues/6 - fixed in upstream V8) - the name file from the customizer tool is identical to the one that comes out of the ICU source distribution (icudt54l.dat) and if I trace the execution it is definitely accessing the correct file, but it just doesn't seem to like it's contents later on:
(This probably needs tagging with intl - FAO @srl295)
The wiki page at https://github.com/joyent/node/wiki/Intl#using-the-small-build suggests that you can use provide additional data at runtime using "a packaged data file /some/path/icudt53l.dat such as from http://apps.icu-project.org/datacustom/"
While I can use the data file that is supplied with the ICU source distribution I cannot get anything from the data customizer tool to work properly - it triggers a memory fault/core dump when I point node at it with the --icu-data-dir parameter and try to use the APIs (for example with the btest402.js mentioned in the wiki)
It's the same failure I get when I point the --icu-data-dir at an empty directory for which there's already an outstanding issue (https://github.com/srl295/node/issues/6 - fixed in upstream V8) - the name file from the customizer tool is identical to the one that comes out of the ICU source distribution (icudt54l.dat) and if I trace the execution it is definitely accessing the correct file, but it just doesn't seem to like it's contents later on:
stat("/dev/shm/dat.icuc/icudt54l.dat", {st_mode=S_IFREG|0644, st_size=28183472, ...}) = 0
open("/dev/shm/dat.icuc/icudt54l.dat", O_RDONLY) = 12
mmap(NULL, 28183472, PROT_READ, MAP_SHARED, 12, 0) = 0x7f2442914000
close(12) = 0
The text was updated successfully, but these errors were encountered: