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: "sean yang" <seanatpurdue at hotmail dot com>
To: vapier at gentoo dot org
Cc: libc-alpha at sourceware dot org
Date: Sat, 11 Mar 2006 21:17:39 +0000
Subject: Re: write() and __libc_write()?
Bcc:

Thanks. My understanding is that __libc_wirte, which is an alias to write, is actually generated from my linux source. i.e., glibc first recoginizes it as a stub, and then uses the linux implementation to fill it.

So, linux implementation is the egg and glibc_write is the chicken in this case. Am I right:)

From: Mike Frysinger <vapier@gentoo.org>
To: "sean yang" <seanatpurdue@hotmail.com>
CC: libc-alpha@sourceware.org
Subject: Re: write() and __libc_write()?
Date: Sat, 11 Mar 2006 00:45:30 -0500
On Saturday 11 March 2006 00:17, sean yang wrote: > 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?

grep is your friend
read manual/maint.texi and sysdeps/unix/make-syscalls.sh
-mike

_________________________________________________________________ Express yourself instantly with MSN Messenger! Download today - it's FREE! http://messenger.msn.click-url.com/go/onm00200471ave/direct/01/

References:
- Re: write() and __libc_write()?
  - From: Mike Frysinger

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