[PATCH] Write errors to stdout and not stderr in wcsmbs/tst-mbrtowc.c

Roland McGrath roland@hack.frob.com
Fri Oct 3 19:36:00 GMT 2014


The dup2 hack is either cute or horrible (likely both).  I don't think we
should do anything like that in one random test.  Rather, we should settle
on a uniform policy for tests and using assert.  It could be that we never
use assert.  Or it could be that we use assert freely and just make
test-skeleton.c always do the dup2 hack itself.  Or it could be something
else I haven't thought of off hand.  But let's get a plan.

If you'd like to convert these tests to use test-skeleton.c first as a
separate change before we figure out how to address the assert issue,
that could go in right away.


Thanks,
Roland



More information about the Libc-alpha mailing list