search for: dyld_stub_pthread_once

...ure. When compiled without libasan as... >>> >>> g++-fsf-4.8 -std=c++98 cond1.C -g -O0 -o cond1_no_asan.exe >>> >>> the resulting executable runs fine. Debugging this in gdb seems to show >>> that the failure >>> is occuring in the final call to dyld_stub_pthread_once (). The same test >>> case >>> compiles fine with -fsanitize=address under llvm 3.2 clang++ and produces >>> no runtime errors >>> but the code execution path is very different in that case (because of the >>> different >>> libstdc++). >>&...

...o produce the above failure. When compiled without libasan as... >> >> g++-fsf-4.8 -std=c++98 cond1.C -g -O0 -o cond1_no_asan.exe >> >> the resulting executable runs fine. Debugging this in gdb seems to show >> that the failure >> is occuring in the final call to dyld_stub_pthread_once (). The same test >> case >> compiles fine with -fsanitize=address under llvm 3.2 clang++ and produces >> no runtime errors >> but the code execution path is very different in that case (because of the >> different >> libstdc++). >> Can you take a quick...

...ress -std=c++98 cond1.C -g -O0 -o cond1_asan.exe to produce the above failure. When compiled without libasan as... g++-fsf-4.8 -std=c++98 cond1.C -g -O0 -o cond1_no_asan.exe the resulting executable runs fine. Debugging this in gdb seems to show that the failure is occuring in the final call to dyld_stub_pthread_once (). The same test case compiles fine with -fsanitize=address under llvm 3.2 clang++ and produces no runtime errors but the code execution path is very different in that case (because of the different libstdc++). Can you take a quick peek at this and determine if this is a darwin pthread or unw...

...nd1_asan.exe > > to produce the above failure. When compiled without libasan as... > > g++-fsf-4.8 -std=c++98 cond1.C -g -O0 -o cond1_no_asan.exe > > the resulting executable runs fine. Debugging this in gdb seems to show > that the failure > is occuring in the final call to dyld_stub_pthread_once (). The same test > case > compiles fine with -fsanitize=address under llvm 3.2 clang++ and produces > no runtime errors > but the code execution path is very different in that case (because of the > different > libstdc++). > Can you take a quick peek at this and determine...

...e. When compiled without libasan as... >>> >>> g++-fsf-4.8 -std=c++98 cond1.C -g -O0 -o cond1_no_asan.exe >>> >>> the resulting executable runs fine. Debugging this in gdb seems to show >>> that the failure >>> is occuring in the final call to dyld_stub_pthread_once (). The same test >>> case >>> compiles fine with -fsanitize=address under llvm 3.2 clang++ and produces >>> no runtime errors >>> but the code execution path is very different in that case (because of the >>> different >>> libstdc++). >>&...

...ut libasan as... >>>> >>>> g++-fsf-4.8 -std=c++98 cond1.C -g -O0 -o cond1_no_asan.exe >>>> >>>> the resulting executable runs fine. Debugging this in gdb seems to show >>>> that the failure >>>> is occuring in the final call to dyld_stub_pthread_once (). The same test >>>> case >>>> compiles fine with -fsanitize=address under llvm 3.2 clang++ and produces >>>> no runtime errors >>>> but the code execution path is very different in that case (because of the >>>> different >>>&g...

...gt; > >>>> g++-fsf-4.8 -std=c++98 cond1.C -g -O0 -o cond1_no_asan.exe > >>>> > >>>> the resulting executable runs fine. Debugging this in gdb seems to > show > >>>> that the failure > >>>> is occuring in the final call to dyld_stub_pthread_once (). The same > test > >>>> case > >>>> compiles fine with -fsanitize=address under llvm 3.2 clang++ and > produces > >>>> no runtime errors > >>>> but the code execution path is very different in that case (because > of the > &...

...g++-fsf-4.8 -std=c++98 cond1.C -g -O0 -o cond1_no_asan.exe > > >>>> > > >>>> the resulting executable runs fine. Debugging this in gdb seems to > > show > > >>>> that the failure > > >>>> is occuring in the final call to dyld_stub_pthread_once (). The same > > test > > >>>> case > > >>>> compiles fine with -fsanitize=address under llvm 3.2 clang++ and > > produces > > >>>> no runtime errors > > >>>> but the code execution path is very different in that ca...

...g++-fsf-4.8 -std=c++98 cond1.C -g -O0 -o cond1_no_asan.exe > > >>>> > > >>>> the resulting executable runs fine. Debugging this in gdb seems to > > show > > >>>> that the failure > > >>>> is occuring in the final call to dyld_stub_pthread_once (). The same > > test > > >>>> case > > >>>> compiles fine with -fsanitize=address under llvm 3.2 clang++ and > > produces > > >>>> no runtime errors > > >>>> but the code execution path is very different in that ca...

...ond1.C -g -O0 -o cond1_no_asan.exe > > > >>>> > > > >>>> the resulting executable runs fine. Debugging this in gdb seems to > > > show > > > >>>> that the failure > > > >>>> is occuring in the final call to dyld_stub_pthread_once (). The > same > > > test > > > >>>> case > > > >>>> compiles fine with -fsanitize=address under llvm 3.2 clang++ and > > > produces > > > >>>> no runtime errors > > > >>>> but the code executio...

...+98 cond1.C -g -O0 -o cond1_no_asan.exe >> > >>>> >> > >>>> the resulting executable runs fine. Debugging this in gdb seems to >> > show >> > >>>> that the failure >> > >>>> is occuring in the final call to dyld_stub_pthread_once (). The same >> > test >> > >>>> case >> > >>>> compiles fine with -fsanitize=address under llvm 3.2 clang++ and >> > produces >> > >>>> no runtime errors >> > >>>> but the code execution path is v...

..._asan.exe > > > > >>>> > > > > >>>> the resulting executable runs fine. Debugging this in gdb seems to > > > > show > > > > >>>> that the failure > > > > >>>> is occuring in the final call to dyld_stub_pthread_once (). The > > same > > > > test > > > > >>>> case > > > > >>>> compiles fine with -fsanitize=address under llvm 3.2 clang++ and > > > > produces > > > > >>>> no runtime errors > > > > &gt...