Displaying 4 results from an estimated 4 matches for "zeroises".
Did you mean:
zeroise
2016 Sep 07
2
Test failures building RELEASE_3.9.0/final
I ran "ninja check-asan" and no errors. But "ninja check-msan" had 117
errors.
I took the first FAILED test, which was for eventfd.cc, and executed the
command
line creating an eventfd executable in a temporary directory and then
executed that file using gdb. Finally, used bt to dump the stack.
I've emailed llvm-admin at lists.llvm.org to setup an account since
2016 Sep 07
2
-fsanitize=memory failing on 3.9.0
I've compiled REALEASE_390/final but all "ninja check-msan" tests are
failing (http://lists.llvm.org/pipermail/llvm-dev/2016-September/104609.html)
I'm waiting for an account to be created to file a bug, but in the
mean time I thought I'd take a look at it myself.
My system is an Arch Linux system that is up to date as of this morning:
$ uname -a
Linux wink-desktop
2016 Sep 07
4
Test failures building RELEASE_3.9.0/final
I've "successfully" built 3.9.0 release but when I run "ninja check-all" I
got 208 Unexpected failures:
Expected Passes : 33997
Expected Failures : 198
Unsupported Tests : 685
Unexpected Failures: 208
Below is the log I captured running "time ninja check-all | tee
ninja-check-all.txt"
https://drive.google.com/open?id=0B-KTY7zi7eZHU2hGYTRtd01QZjA
2014 Jan 28
3
[PATCH] Proposal for a pacifier option with mkdiskimage
Hi,
me:
> > [mkdiskimage] -s does not prevent zeroizing on block device. Probably
> > because truncate() fails.
hpa:
> Yes, we should probably fix that. The tool was originally designed for
> images, not for hardware devices, and it doesn't make much sense to zero
> the whole hardware device like that.
Maybe for privacy reasons ?
But indeed: -s should skip zeroizing,