Problem with exec and uclibc

[Joakim Tjernlund]

On Tue, 2008-03-25 at 16:48 +0100, andres wrote:
> Hi all. We are developing and application over uclibc and busybox on a 
> mips architecture.
> 
> In addition, we are using an Erlang Virtual Machine. The problem is that

Cool, Erlang on uClibc :) Did some programming in Erlang in the
early days when it still was impl. in Prolog.

>  
> this one fails when we try to access to system. Example:
> 
> 4> os:cmd("ls /").
> []
> 
> 5> open_port({spawn, "ls"}, []).
> #Port<0.91>
> 6> flush().
> ok
> 
> As we see, the above commands doesn't list anything.
> 
> We think underlaying Virtual Machine uses "exec" family calls and these 
> ones crash. In fact, we have made some tests with little programs. We 
> compile the same source code to x86 and mips and then, we saw different 
> behaviors.

You should strace erlang to see what it does.

> 
> The above results have led us to anticipate that glibc is robuster than 
> uclibc and supports some warnings. In such a case we can think that 
> Erlang VM. Have anybody an idea about this?

glibc may be robuster, or more forgiving against misuse, than uClibc in
some areas, but as already pointed out you seem to misuse the execv
interface. 

 Jocke
> 
> Thanks,
> Andrés Estévez
>