From owner-freebsd-hackers Sun Oct 28 22:42:55 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from warez.scriptkiddie.org (uswest-dsl-142-38.cortland.com [209.162.142.38]) by hub.freebsd.org (Postfix) with ESMTP id 03CA437B401 for ; Sun, 28 Oct 2001 22:42:52 -0800 (PST) Received: from [192.168.69.11] (unknown [192.168.69.11]) by warez.scriptkiddie.org (Postfix) with ESMTP id 5C09762D01 for ; Sun, 28 Oct 2001 22:42:51 -0800 (PST) Date: Sun, 28 Oct 2001 22:43:00 -0800 (PST) From: Lamont Granquist To: Subject: MT-Safe wrapper around memcpy()? Message-ID: <20011028223152.K5909-100000@coredump.scriptkiddie.org> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG I'm trying to figure out the best way to write a wrapper around memcpy() which can call fprintf() without winding up getting into a recursive loop. The problem is that fprintf() will call memcpy() and around and around we go. I can use a global variable to prevent this, but that usage isn't thread safe. I can make it thread safe by using pthread keys, but then i have to link in libc_r, and for non-pthreaded programs i don't want to do that. Anyone have any suggestions? Right now I'm almost thinking that I just need to directly patch libc and libc_r. It might be an ugly patch though, and I'd rather not have this patch mandate recompiling all of libc. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message