similar to: [msan] Failing mmap.cc test

Evgenii Stepanov <eugeni.stepanov at gmail.com> writes: > See https://reviews.llvm.org/D51364 - a very similar bug was > introduced by a compiler-rt change and then fixed by a revert. Ok, so what do we do about this? D50940 seems to have introduced the problem but it was reverted. The "tentative fix" in D51364 was abandoned but it's not clear to me why (maybe because

HOwdy I read R books about scale function for variable transformation. Acoording to this book scale function leads me to better regression results. Or am I worng? I hope somebody tell me about a scale function? Is it for variable transformation? -- Kum-Hoe Hwang, Phone : 82-31-250-3516Email : phdhwang@gmail.com [[alternative HTML version deleted]]

Scenario: Our Asterisk 13 PBX (on network 192.168.254.0/24, bound to 192.168.254.1:5060) is behind a NAT, acting as a client to our ITSPs SIP server. But also, this Asterisk is server for various VoIP telephones. Acoording to Asterisk's wiki, the transport section of pjsip.conf is configured as follows: ; Transport via UDP [transport-nat-udp] type= transport

Hi, Porting msan to the Cavium T99 chip requires a VMA mapping of 4TB. The brute-force way of doing this would be by collecting memory segments that weren't mapped - from the results of the msan test harness - and creating mapped segments ranges. Lather, rinse, repeat until all the addressable segments are mapped in msan.h. But I was wondering if there isn't a more efficient way of

On 3 Mar 2018, at 13:10, David CARLIER via llvm-dev <llvm-dev at lists.llvm.org> wrote: > > Hi dear FreeBSD support, > > The turn of MemorySanitizer to get early support into FreeBSD. Thanks David, what are your plans? Sorry for slacking off on your other sanitizer reviews for FreeBSD. I have been busy on too many other things. :( -Dimitry -------------- next part

On 03.03.2018 13:10, David CARLIER via llvm-dev wrote: > Hi dear FreeBSD support, > > The turn of MemorySanitizer to get early support into FreeBSD. > > Kind regards. > I recommend to fix the failures in existing tests. Next enable MSan for sanitizer-common tests and fix the breaking tests on FreeBSD. How about TSan? -------------- next part -------------- A non-text

In the example below, the Memory Sanitizier (from clang 3.3) reports an error: #include <math.h> int main() { double x; (void) modf(0, &x); if (x) { // Boom return 1; } return 0; } I see that modf() is not implemented by compiler-rt. Is it possible to make the Memory Sanitizer assume that all un-instrumented functions initialize any pointers arguments?

Hi dear FreeBSD support, The turn of MemorySanitizer to get early support into FreeBSD. Kind regards. -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20180303/253c2a4f/attachment.html>

On Thu, Jan 22, 2015 at 2:33 AM, Evgeniy Stepanov <eugenis at google.com> wrote: > On Wed, Jan 21, 2015 at 8:46 PM, Rafael Espíndola > <rafael.espindola at gmail.com> wrote: > >> What about creating an msan interface DSO for the purposes of > satisfying -z > >> defs? The executable will always be searched first, so the interface DSO > >> could be

I recently tried to enabled building llvm libraries with -Wl,-z,defs. The intention was to detect missing dependencies on ELF, so that we don't get into a situation where a .so builds, but the equivalent .dylib or .dll fails. This failed when building with msan because of undefined references to functions like __msan_memcpy. Unfortunately, I don't think elf linkers have a way of

> What about creating an msan interface DSO for the purposes of satisfying -z > defs? The executable will always be searched first, so the interface DSO > could be empty or full of ud2a. I like the idea. The ideal solution would probably be for the linkers to have a --not-needed command line option that prevents the .so from going in the DT_NEEDED, but one with just stubs is probably

Hello everybody, I've run into some strange behavior with memory sanitizer that I can't explain and hope somebody with more knowledge of the implementation would be able to help me out or at least point me into the right direction. For background, I'm using memory sanitizer to check Julia (julialang.org), which uses (or at least will once I track down a few bugs) MCJIT for the code

I assume there are transitions between JITted code and native helper functions. How are you handling them? Are native functions MSan-instrumented? MSan is passing shadow across function calls in TLS slots. Does your TLS implementation guarantee that accesses to __msan_param_tls from JITted and from native code map to the same memory? On Mon, Jan 27, 2014 at 11:36 PM, Evgeniy Stepanov

I have verified that both TLS implementations indeed find the same area of memory. Anything else I could look for? On Tue, Jan 28, 2014 at 4:28 PM, Keno Fischer <kfischer at college.harvard.edu>wrote: > Yes, both JIT code and the native runtime are instrumented. I am under the > impressions that the the C library should guarantee that from the way the > relocations are

How is ccall() implemented? If it manually sets up a stack frame, then it also needs to store argument shadow values in paramtls. I don't think there is an overflow, unless you have a _lot_ of arguments in a function call. On Sun, Feb 2, 2014 at 9:26 AM, Keno Fischer <kfischer at college.harvard.edu> wrote: > Also, I was looking at the instrumented LLVM code and I noticed that the

Hi, I had posted the following issue a few days ago in Xen-users but I haven''t received any answer yet. So I decided to re-post it here in hope for some solution. Here''s the original post: Xen wiki states that using linux 3.0 and above as dom0 works with all graphics cards. I could install the fglrx graphics driver on my desktop machine with a discrete graphics card (Radeon

The code for ccall looks right. Sounds like you have a very small range of instructions where an uninitialized value appear. You could try debugging at asm level. Shadow for b should be passed at offset 0 in __msan_param_tls. MSan could propagate shadow through arithmetic and even some logic operations (like select). It could be that b is clean on function entry, but then something uninitialized

I'm seeing some test failures for unit tests for msan (check-msan) happening in googletest, which I find weird. I'm on Arch Linux, with r342711. Below is one type of error that I see. The full log is 416MB (!) big. My guess is that those errors are related, but if anyone needs the full log, I'll provide it. Here is a reduced log from the end:

Hi, I am new to ipsec and trying to connect my bsd server with win 2000. I have succeeded to tunnel using pre-shared key. But regarding certificate , I failed to get success. The following are configuration : racoon.conf path certificate "/usr/local/openssl/certs" ; # "log" specifies logging level. It is followed by either "notify",

Keir, Here''s a first patch to address the issue with rolling over to guest-physical address 0x00000000 when assigning address regions to PCI BARs during HVM boot. For now, this: - Makes the hole bigger: 0xC0000000-0xF5000000. This might be overkill...but it should only matter for 32-bit guest OSes assigned more than 3GB of RAM. - Prevents addresses from above 0xF50000000 from