Date: Sun, 23 Nov 2003 15:04:34 +0100 From: Adriaan de Groot <adridg@cs.kun.nl> To: amd64@freebsd.org Subject: Re: Ports mixing libc and libc_r Message-ID: <200311231504.35012.adridg@cs.kun.nl> In-Reply-To: <200311231347.38353.adridg@cs.kun.nl> References: <200311231347.38353.adridg@cs.kun.nl>
next in thread | previous in thread | raw e-mail | index | archive | help
--Boundary-00=_z5Lw/2I7qZkRQQX Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline On Sunday 23 November 2003 13:47, Adriaan de Groot wrote: > ogg123 bus errors on me all the time, in code that looks perfectly > innocuous sprintf(data,"%05li:%05.2f",min,sec); > and i suspect it's because ogg123 links against both libc_r and libc: Duh, that's not a problem at all. However, sprintf() and fprintf() both have trouble printing double arguments from a thread that is not the main thread of control on amd64, as the attached little test program shows. I compile it on 5-CURRENT (well, from last week) with: beans.ebn.kun.nl$gcc -o threadtest t.c -pthread -- pub 1024D/FEA2A3FE 2002-06-18 Adriaan de Groot <groot@kde.org> If the door is ajar, can we fill it with door-jamb? --Boundary-00=_z5Lw/2I7qZkRQQX--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200311231504.35012.adridg>