search for: xsan

...itizers like TSan. * The architecture of the existing symbolizer makes it cumbersome to support inline frames. * The architecture of the existing symbolizer is sequential which prevents performing batched symbolication of stack frames. # Tools The proposed tools would be a sub-tools of a new llvm-xsan tool. E.g. llvm-xsan <subtool> Sub-tools will support nesting of sub-tools to allow building ergonomic tools. E.g.: llvm-xsan asan <asan subtool> * The tools would be part of compiler-rt and will optionally ship with this project. * The tools will be considered experimental while b...

...differently about this. Even if we go down the route of having the sanitizers supporting machine-readable output I'd still like there to be an in-tree tool that supports doing offline symboliation on the machine readable output. So there still might be a case for having the proposed "llvm-xsan" tool in-tree. > It'd be interesting to know more about what problems the valgrind XML format have had and how/whether different solutions would address/avoid those problems. Also might be good to hear about how other tools are parsing the output - whether or not/how they might benefit...

...name sucks, please suggest alternatives). Same for platform-specific code: "/lib/arm/"->"/lib/core/arm", "/lib/i386"->"/lib/core/i386" etc. b) "/BlocksRuntime"->"/lib/BlocksRuntime" c) "/lib/sanitizer_common", "/lib/xsan", "/lib/profile" are not moved. 2. tests: all tests (lit tests and unit tests) are moved from directories under "/lib" to "/test" to be consistent with LLVM/Clang test subtrees. See the original mail from Chandler for the overview of compiler-rt tree current sta...

...rote: >> >>> > we would still want to use compiler-rt test-suite in a standalone >>> mode, to test fully built/installed toolchains, >>> and even GCC. >>> >>> Sounds good. >>> >>> >>> > Clang driver links the static xsan runtimes from a hardcoded >>> > paths in Clang resource directory, and doesn't add flags like >>> > "-lasan -L/path/to/clang/resource/dir". I find this behavior >>> reasonable. >>> >>> Can we change the flags to "-lasan -L/path/t...

..., Apr 3, 2014 at 5:04 AM, Greg Fitzgerald <garious at gmail.com> wrote: > > we would still want to use compiler-rt test-suite in a standalone mode, > to test fully built/installed toolchains, > and even GCC. > > Sounds good. > > > > Clang driver links the static xsan runtimes from a hardcoded > > paths in Clang resource directory, and doesn't add flags like > > "-lasan -L/path/to/clang/resource/dir". I find this behavior reasonable. > > Can we change the flags to "-lasan -L/path/to/clang/resource/dir"? If > we make...

Hi ! As some of you might know, Apple has discontinued it's xServes server as of january 31st 2011. We have a server rack with 12 xserves ranging from dual G5's to dual quand-core xeon lastest generation, 3 xserve-raid and one activeraid 16 TB disk enclosure. We also use xSan to access a shared file system among the servers. Services are run from this shared filesystem, spreaded across the servers. Some LUNs on the fiber channel network are accessed directly and mounted on a case-by-case basis. Those raid volumes are partitioned with a GUID partition map, and apple_...

Lately it never fails when I attach a Mac running OSX 10.5 that I get runaway pid's. I tracked them down so far to multiple close_wait's: # /usr/sbin/lsof | grep pbg5mac smbd 24876 root 6u IPv4 80015755 TCP yoda.wrenkasky.com:netbios-ssn->pbg5mac.wrenkasky.com:49381 (CLOSE_WAIT) They can grow to over 100 if I don't catch it or nobody can log on anymore ;-)

...ompiler-rt test-suite in a standalone >>>>> > mode, to test fully built/installed toolchains, >>>>> and even GCC. >>>>> >>>>> Sounds good. >>>>> >>>>> >>>>> > Clang driver links the static xsan runtimes from a hardcoded >>>>> > paths in Clang resource directory, and doesn't add flags like >>>>> > "-lasan -L/path/to/clang/resource/dir". I find this behavior >>>>> > reasonable. >>>>> >>>>> Can...

...y libs to the just-built-clang install directory. > This is possible, but please keep in mind that: 1) we would still want to use compiler-rt test-suite in a standalone mode, to test fully built/installed toolchains, and even GCC. 2) Adding -L... wouldn't work: Clang driver links the static xsan runtimes from a hardcoded paths in Clang resource directory, and doesn't add flags like "-lasan -L/path/to/clang/resource/dir". I find this behavior reasonable. I don't see a problem with the current approach - we can make "run sanitizer test suite" command in the top-l...

...> > mode, to test fully built/installed toolchains, >> >>>>> and even GCC. >> >>>>> >> >>>>> Sounds good. >> >>>>> >> >>>>> >> >>>>> > Clang driver links the static xsan runtimes from a hardcoded >> >>>>> > paths in Clang resource directory, and doesn't add flags like >> >>>>> > "-lasan -L/path/to/clang/resource/dir". I find this behavior >> >>>>> > reasonable. >> >>&g...

...san/ and friends, but maybe the > sanitizer folks have objections to that. consistency seems a compelling > reason here, but there might be other compelling concerns. > Yes, I don't like the way testing is organized either. Originally it made sense to put sanitizer lit tests under lib/xsan/, but now we've got a lot of sanitizers, and a lot of duplicating configuration code. As Renato mentioned, browsing through lit configs is a bit painful. I would like to proceed with re-organizing the tests for sanitizers, unless anyone objects. Kostya? > Now, the build system has always b...

...t alternatives). Same for platform-specific code: > "/lib/arm/"->"/lib/core/arm", "/lib/i386"->"/lib/core/i386" etc. > > b) "/BlocksRuntime"->"/lib/BlocksRuntime" > > c) "/lib/sanitizer_common", "/lib/xsan", "/lib/profile" are not moved. > > > > 2. tests: > > all tests (lit tests and unit tests) are moved from directories under > "/lib" to "/test" to be consistent with LLVM/Clang test subtrees. > > > > See the original mail from Chan...

...suggest alternatives). Same for platform-specific code: "/lib/arm/"->"/lib/core/arm", "/lib/i386"->"/lib/core/i386" etc. >> b) "/BlocksRuntime"->"/lib/BlocksRuntime" >> c) "/lib/sanitizer_common", "/lib/xsan", "/lib/profile" are not moved. >> >> 2. tests: >> all tests (lit tests and unit tests) are moved from directories under "/lib" to "/test" to be consistent with LLVM/Clang test subtrees. >> >> See the original mail from Chandler for...

A question about capturing videos to a Samba share... When Apple's Final Cut Pro captures video files, it pre-allocates file space on the destination volume. If you capture to a local volume that's physically attached to a Macintosh, or if you capture to a network volume via AFP (Apple File Sharing Protocol), you can see that Final Cut instantly creates a file of the

Hi, I've run into a bit of a problem and exhausted my knowledge and research. I'm hoping that I've overlooked something very obvious! I moved from a single Apple OS X 10.6.2 server Dovecot environment to a NFS clustered environment, currently with two servers. Both servers are identical hardware, software. Currently both the Dovecot index and data files are on the NFS RAID array.

...ut maybe the > sanitizer folks have objections to that. consistency seems a compelling > reason here, but there might be other compelling concerns. > > > > Yes, I don't like the way testing is organized either. Originally it > made sense to put sanitizer lit tests under lib/xsan/, but now we've got a > lot of sanitizers, and a lot of duplicating configuration code. As Renato > mentioned, browsing > > through lit configs is a bit painful. I would like to proceed with > re-organizing the tests for sanitizers, unless anyone objects. Kostya? > > > &...

On 30 January 2014 21:50, Reid Kleckner <rnk at google.com> wrote: > > I don't see any compelling reason to split the sanitizers out today. > Clear, next. I think the sanitizer guys would probably take a patch to CMakeLists.txt to > disable the sanitizer RTLs. > Right. I'll first make it build and test, than I'll disable via a flag, since other people can work

It does sound like Android is better suited for "honest" cross-compilation, rather than "build compiler-rt for all targets we can find" model. I'm still not convinced that we must require the "ninja install" step. Could we just "ninja clang" and then build the second stage against the first stage build directory? Will this "find_package" thing

We''re trying to set up a colocated server for deploying a Rails application or three. Right now I''m undecided between a PC-based server running FreeBSD and an Xserve running OS X. I''ve never colocated before so I''m wondering if anyone has stories, tips, or could say what their preferred OS is for running Rails. I''m also wondering how performance of