Date: Mon, 29 Oct 2001 00:53:16 -0600 From: Alfred Perlstein <bright@mu.org> To: Lamont Granquist <lamont@scriptkiddie.org> Cc: freebsd-hackers@freebsd.org Subject: Re: MT-Safe wrapper around memcpy()? Message-ID: <20011029005316.W15052@elvis.mu.org> In-Reply-To: <20011028223152.K5909-100000@coredump.scriptkiddie.org>; from lamont@scriptkiddie.org on Sun, Oct 28, 2001 at 10:43:00PM -0800 References: <20011028223152.K5909-100000@coredump.scriptkiddie.org>
next in thread | previous in thread | raw e-mail | index | archive | help
* Lamont Granquist <lamont@scriptkiddie.org> [011029 00:43] wrote:
>
> 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.
Where do you see mem* calling printf?
--
-Alfred Perlstein [alfred@freebsd.org]
'Instead of asking why a piece of software is using "1970s technology,"
start asking why software is ignoring 30 years of accumulated wisdom.'
http://www.morons.org/rants/gpl-harmful.php3
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-hackers" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20011029005316.W15052>