similar to: Q about msan : mapping 4TB

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

Am 19.08.2015 um 19:07 schrieb Steve Edwards: > Please don't top post. > > On Wed, 19 Aug 2015, James Cass wrote: > >> Steve, would you be willing to share that "quick bash script"? > > There's no magic in the script, but here it is, embarrassing myself: > > cp sample-call-file /tmp/ > chmod +x /tmp/sample-call-file >

On Tue, Dec 2, 2014 at 3:14 PM, Warren Young <wyml at etr-usa.com> wrote: > > >> What part of the breakage that NetworkManager does is good for a >> wired, static-addressed server? > > If you disable NM, the network configuration GUI stops working in EL7. (I didn?t do much with EL6, but I thought its GUI had a fall-back for the non-NM case.) > > We don?t need

On Wed, 26 Feb 2020, Nicolas Kovacs wrote: >Some time ago I had SELinux problems with Fail2ban. >Unfortunately when I install [...] from EPEL, I still get the same error. EPEL packages are often crap quality (as packages), merely blind imports of the upstream package without any adjustments needed for the RHEL/CentOS environment (sometimes not even for Fedora), which is often somewhat

/> Additionally, it has been stated many times that you / /> _should_ _never_ _transcode_ _any_ _lossy_ _codec_. / This isn't transcoding. The point about transcoding, say, MP3->OGG is that the two codecs use different assumptions (psychoacoustic models, etc.) in performing the compression -- so transcoding often results in one codec trying to chase down and reproduce artifacts

https://bugzilla.mindrot.org/show_bug.cgi?id=2514 Bug ID: 2514 Summary: Usability: Key filenames / extensions make sharing private key likely. Product: Portable OpenSSH Version: -current Hardware: All OS: All Status: NEW Severity: minor Priority: P5 Component:

>Message: 10 >Date: Wed, 26 Jan 2005 17:53:39 -0500 (EST) >From: "Sean A. Newton" <nester-asterisk@wewt.net> >Subject: Re: [Asterisk-Users] Re: Polycom and call waiting again.. >To: Asterisk Users Mailing List - Non-Commercial Discussion > <asterisk-users@lists.digium.com> >Message-ID: >

I've been working on this issue for quite a while. Back in January of 2015 I posted about how well external monitors worked with the out-of-the-box CentOS 7 ATI radeon drivers and my Dell M6500 with an ATI FirePro M7820. At the time the support was seamless and 'Just Worked' without any issue. A few months later, some update came down the pipe and this broke completely, with the

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

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'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:

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

> 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

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

I am having the same trouble with automatically mounted home shares with samba 2.2.1a (PDC, domain logins, roaming profiles) and NT4WS sp6a. If I login as one user, logout, then login as another, I can view the previous users home share as well as my newly logged in users home share (lather, rinse, repeat...). The NT box has a machine account, domain logins work, profiles work, login scripts

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

Is there anything I can do regarding the linker issue? The solaris linker is in /usr/ccs/bin/ld but I think llvm wants to use the gnu linker. gcc in my system was compiled with the solaris linker. Thanks, Jorge On Mon, Jun 24, 2013 at 6:18 PM, Stefan Teleman <stefan.teleman at gmail.com>wrote: > On Mon, Jun 24, 2013 at 6:17 PM, Jorge Rodrigues <skeept at gmail.com> wrote: >

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

Looks like when you materialize the stores, you should check the size of the the store and emit an appropriate amount of stores to the origin shadow (or just a memset intrinsic?). On Wed, Feb 5, 2014 at 2:13 PM, Keno Fischer <kfischer at college.harvard.edu>wrote: > The @entry stuff is just a gdb artifact. I've been tracking this back a > little further, and it seems there's

Yes, it would be great to get that fixed. On Wed, Feb 5, 2014 at 4:09 PM, Evgeniy Stepanov <eugeni.stepanov at gmail.com>wrote: > On Thu, Feb 6, 2014 at 12:21 AM, Keno Fischer > <kfischer at college.harvard.edu> wrote: > > Looks like when you materialize the stores, you should check the size of > the > > the store and emit an appropriate amount of stores to the