Hi Thorsten, I have found a solution to this problem from redhat's libc mailing list. http://sources.redhat.com/ml/libc-alpha/2004-12/msg00006.html This link provides the alternative approach for this issue with the latest glibc. rgs, Syed Buhari -----Original Message----- From: Thorsten Kukuk [mailto:kukuk@suse.de] Sent: Wednesday, December 15, 2004 7:42 PM To: Syed Mohd Buhari Cc: Krishna Murthy; Santosh Siddheshwar; Raghavan Gurumurthy; Dipak Patel Subject: Re: [SLE] Missing __libc_write symbol in glibc on SuSe9.2 On Wed, Dec 15, Syed Mohd Buhari wrote:

Hi Thorsten,

Thanks for your reply.

Actually there is no restriction on using __libc_... functions.

the symbol name begins with two underlines. Which means this is a glibc internal symbol and you are not allowed to use it. Which else restriction do you need?

As my understanding, glibc exports syscall (eg. write) as weak symbol and other symbol (eg., __libc_write) as strong symbol. Thus user can override the pure syscalls.

__libc_* functions are for internal glibc use (for example libphtread or librt) and nothing else. They are not for overwriting from applications. Thorsten -- Thorsten Kukuk http://www.suse.de/~kukuk/ kukuk@suse.de SuSE Linux Products GmbH Maxfeldstr. 5 D-90409 Nuernberg -------------------------------------------------------------------- Key fingerprint = A368 676B 5E1B 3E46 CFCE 2D97 F8FD 4E23 56C6 FB4B