This is the mail archive of the
libc-alpha@sourceware.org
mailing list for the glibc project.
Re: write() and __libc_write()?
- From: Mike Frysinger <vapier at gentoo dot org>
- To: libc-alpha at sourceware dot org
- Cc: "sean yang" <seanatpurdue at hotmail dot com>
- Date: Fri, 10 Mar 2006 23:47:30 -0500
- Subject: Re: write() and __libc_write()?
- Geoman: IS A RETARD
- References: <BAY105-F1640497A651B3120C647F0C0E20@phx.gbl>
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
-mike