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]

Re: write() and __libc_write()?




From: Mike Frysinger <vapier@gentoo.org>
To: libc-alpha@sourceware.org
CC: "sean yang" <seanatpurdue@hotmail.com>
Subject: Re: write() and __libc_write()?
Date: Fri, 10 Mar 2006 23:47:30 -0500

On Friday 10 March 2006 23:10, sean yang wrote:
> this is the code from ./ sysdeps/generic/write.c, and I believe it's the
> code corresponding to write(2) exported by #include <unistd.h>
> By why can't I find "int $0x80" inside the function body?


no, that is the generic write.c that is only used if the target doesnt provide
its own version of write


in the case of unix (and thus linux) targets, there is no "write.c" file, but
rather it's autogenerated afaik from the sysdeps/unix/syscalls.list file
Ok, thanks for the info. But syscalls.list tells us " write - write Ci:ibn __libc_write __write write".
i.e., write is alias to __libc_write. But, how __libc_write is generated? It seems to be an egg/chicken in this file. After all, libc.so.6 should be produced from the glibc source tarball. So there should be source file corresponding to write()/__glibc_write somewhere.


-mike

_________________________________________________________________
Don?t just search. Find. Check out the new MSN Search! http://search.msn.click-url.com/go/onm00200636ave/direct/01/



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