[ECOS] how work synthetic for exceptions
Wed Apr 9 09:46:00 GMT 2008
On Wed, Apr 09, 2008 at 09:19:57AM +0100, trollepi jj wrote:
> We have successfully implement the same mecanism (a kind of softirq) on the synthetic target. We modify and add some structures to meet the requirements of linux signal implementation.
> But we have a conception question :
> Why do you coding the call of the syscall in the file syscall-i386-linux-1.0.S? Is it impossible for the synthetic to call directly a syscall (confusion between gnu/linux libC and eCos lib, stack issues)?
Correct. eCos does not link with the native libc, it directly calls
kernel system calls. There is no way to tell the linker that a call to
read() in file X.c should call the native glibc read() function, but a
call to read() in Y.c should call the eCos libc read function.
Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos
and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss
More information about the Ecos-discuss