glibc segfault on "special" long double values is _ok_!?

[Mike Frysinger]

On Thursday 07 June 2007, Jan-Benedict Glaw wrote:
> On Wed, 2007-06-06 22:44:17 +0100, James Youngman <jay@gnu.org> wrote:
> > If I read a stream of data (from a file, a network socket, etc.) which
> > is supposed to contain valid floating-point data, it is reasonable for
> > a program to print it.  Especially so if the printing I am doing is a
>
> Data you didn't compute yourself isn't supposed to contain anything
> known. Each and every bit may contain something you didn't expect,
> that's why you have to do input checking.

yes, but the question is where do the robustness checks live ... every single 
application out there or glibc ?  consider a game transmitting/receiving 
floating point data over the network and logging the results ... should the 
game assume that the library isnt going to crash when feeding values into 
printf() or need it check every value itself ?
-mike
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 827 bytes
Desc: This is a digitally signed message part.
URL: <http://sourceware.org/pipermail/libc-alpha/attachments/20070607/a463dc4a/attachment.sig>