On Wed, 6 Jul 2016, Zhangjian (Bamvor) wrote:I run test glibc testsuite in previous glibc version with v6 kernel patch
correct or not. After learn and compare some fuzz tools, I feel that there is
no such fuzz tools could help me. So, I wrote a new fuzz tools base on the
trinity and it found several wrapper issues in glibc. I will first explain the
different with existing fuzz tools and paste my propsosal in the end.
I'm not at all clear on whether any of the people working on AArch64 ILP32
glibc have run the glibc testsuite and investigated the results in detail
(the patch submissions have failed to include glibc testsuite results and
have included bugs that would have been detected by the glibc testsuite).
But, if you've found bugs in a new glibc port that were not detected byIt is good idea. I will review the fixed issues(such as wrong context in
the existing testsuite, then tests for those bugs should be contributed to
glibc (even if no existing port has those bugs, improving the test
coverage is still a good idea).