'read' function in uClibc 0.9.32

[unifoxz]

What is the first function run in uClibc when user application call read(...)?

I only could find

_syscall3(ssize_t, read, int, fd, __ptr_t, buf, size_t, count)
#ifndef __LINUXTHREADS_OLD__
libc_hidden_def(read)
#else
libc_hidden_weak(read)
strong_alias(read,__libc_read)
#endif

under uClibc-0.9.32\libc\sysdeps\linux\common\read.c.

Thank you.

[BrianMicek]

What is the first function run in uClibc when user application call read(...)?

I only could find

_syscall3(ssize_t, read, int, fd, __ptr_t, buf, size_t, count)
#ifndef __LINUXTHREADS_OLD__
libc_hidden_def(read)
#else
libc_hidden_weak(read)
strong_alias(read,__libc_read)
#endif

under uClibc-0.9.32\libc\sysdeps\linux\common\read.c.

Thank you.

Hi unifoxz,
Read is a system call ... its not a library call. I don't have a solid understanding of the mechanics of how this works to be honest, but the interface is usually something like <syscall.h>. When a user space application issues a system call, the call is translated into an integer and the associated data is passed to the kernel in one of two ways. The use space application usually blocks waiting for the kernel to complete its system call. I don't think you'll find a "C" interface in (uc)libc.so, but like I said ... I'm not an expert here.

[barunparichha]

get the call sequence using some debugging tool like strace.