This is the mail archive of the libc-alpha@sourceware.org mailing list for the glibc project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Which will happen if I use different LC_COLLATE version?


Hi,

I have a arm board using glibc-2.3.2, now I am going to let it support
zh_CN.utf-8 locale, so I need to have the LC_* files... Because
localedef program consumes too much memory so I can't run it in my
board.

Then I copy all the LC_* files from my PC to arm board. In PC the
glibc version is 2.4, so the different version cause different magic
number in the beginning of the file.

I manually changed the magic number then finally the locale can work
by simple test using gettext()..., every thing goes ok when i run a
simple test program.

But when I run a large program which invokes

1 Thread 16384  0x40953490 in __wcscoll (s1=0xbfffb4a4, s2=0xbfffb4d4)
at strcoll.c:522

It cause SEGV signal, by checking the code I found the fault is
related to LC_* settings.

So I wonder if the problem is caused by I copy the incompatible
version of LC_* files?

Thanks in advance.

Bin


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]