RE: [Linphone-developers] Segmentation violation

[Micha Nelissen]

Simon Morlat wrote:
> I still think that it's a threading issue related with
> compiler/system or compiler option. 
> Did you rebuild a linphone on your pentium M without using CFLAGS,
> install and test it and see if valgrind still complains ? 

It doesn't complain anymore with 1.5.0 here on Pentium M.

I'm trying strace this time on ARM system. There are 4 threads creates
AFAICS: 379, 380, 381, and 382. When 382 begins to run it does:

382   getpid()                          = 382
382   rt_sigprocmask(SIG_SETMASK, [RTMIN], NULL, 8) = 0
382   timer_delete(0)                   = 0
382   old_mmap(NULL, 4290711552, PROT_READ|PROT_WRITE,
MAP_PRIVATE|MAP_ANONYMOUS, 0, 0) = -1 ENOMEM (Cannot allocate memory)
382   old_mmap(NULL, 4290711552, PROT_READ|PROT_WRITE,
MAP_PRIVATE|MAP_ANONYMOUS, 0, 0) = -1 ENOMEM (Cannot allocate memory)
382   --- SIGSEGV (Segmentation fault) @ 0 (0) ---

Tries to allocate a lot of memory! Unfortenately, gdb does not work on
this system. Any idea for the reason of this huge memory allocation ?

Micha