just saw a bizarre case on RH-6.0 where a second call into the dst library in test2 of bin/tests/dst/t_dst looked like it either messed up the stack or there is a compiler bug of some sort because the results didn't get reported, ie code got skipped. this changed causes the report generator to flag tests that don't report results.
just saw a bizarre case on RH-6.0 where a second call into the dst library
in test2 of bin/tests/dst/t_dst looked like it either messed up the
stack or there is a compiler bug of some sort because the results
didn't get reported, ie code got skipped. this changed causes the
report generator to flag tests that don't report results.

each/bind9-collab,pecharmin/bind9,pecharmin/bind9,each/bind9-collab,pecharmin/bind9,each/bind9-collab,pecharmin/bind9,each/bind9-collab,each/bind9-collab,each/bind9-collab,pecharmin/bind9,pecharmin/bind9