search

staticanalysis / data-race-test

Automatically exported from code.google.com/p/data-race-test
0 stars 0 forks source link

go tsan not building #88

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago 
What steps will reproduce the problem?
1. cd tsan/go
2. make
3.

What is the expected output? What do you see instead?
With both gcc and llvm-gcc there is a linker error on goCallbackCommentPc

→  DEBUG=1 make 
g++ go_rtl.cc -I../tsan -I../dynamic_annotations -fno-exceptions -fPIC -DTS_GO 
-Wall -fno-inline -g -D_DEBUG -DDEBUG -m32 -c -o tsan_go32.o
g++ -o libtsan_go32.so x86-ts_util.o x86-suppressions.o x86-common_util.o 
x86-ignore.o x86-thread_sanitizer.o x86-ts_atomic.o -m32 -shared tsan_go32.o
Undefined symbols for architecture i386:
  "_goCallbackCommentPc", referenced from:
      PcToStrings(unsigned long, bool, std::basic_string<char, std::char_traits<char>, std::allocator<char> >*, std::basic_string<char, std::char_traits<char>, std::allocator<char> >*, std::basic_string<char, std::char_traits<char>, std::allocator<char> >*, int*)in tsan_go32.o
ld: symbol(s) not found for architecture i386
collect2: ld returned 1 exit status
make: *** [libtsan_go32.so] Error 1

and a much more verbose one from gcc.

What version of the product are you using? On what operating system?

tsan trunk, OS X, gcc 4.6 and llvm-gcc 4.2.1

Original issue reported on code.google.com by j...@somethingsimilar.com on 19 Feb 2012 at 3:14

GoogleCodeExporter commented 9 years ago 
Information of Go version would be useful. For instance, we are not ready
for go tool at the moment (Issue 87).

Also, no guarantees for i386 just yet. Only linux+amd64.

Original comment by mpime...@google.com on 19 Feb 2012 at 6:00

GoogleCodeExporter commented 9 years ago

Original comment by mpime...@google.com on 19 Feb 2012 at 6:01

GoogleCodeExporter commented 9 years ago 
This is my fault. I was building on OS X because I missed the linux 
instructions. Apologies.

Original comment by j...@somethingsimilar.com on 19 Feb 2012 at 6:16

GoogleCodeExporter commented 9 years ago

Original comment by mpime...@google.com on 24 May 2012 at 6:33