Displaying 2 results from an estimated 2 matches for "vgpreload___".
Did you mean:
vgpreload_
2013 May 30
0
[LLVMdev] unexpectedly loop hanging
...lex/llvm/Release+__Asserts/bin/opt)
> ==5134== by 0x41AE4D2: (below main) (libc-start.c:226)
> ==5134== Address 0x46cfa40 is 0 bytes after a block of size 200 alloc'd
> ==5134== at 0x402C454: operator new[](unsigned int) (in
> /usr/lib/valgrind/vgpreload___memcheck-x86-linux.so)
> ==5134== by 0x4037AE0: (anonymous
> namespace)::Hello::__runOnModule(llvm::Module&) (in
> /home/alex/llvm/Release+__Asserts/lib/Hello.so)*/
>
> ==5134== Address 0x46cfa40 is 0 bytes after a block of size 200 alloc'd...
2013 May 30
2
[LLVMdev] unexpectedly loop hanging
Hello Duncan,
Thank you for your quick answer. I use the standard Makefile from a pass,
that is calling Makefile.common. I saw only the make -d option, that "*print
lots of debugging information*", as mentioned by LLVM.
Using this, valgrind don't tell me extra info. It is a very good idea ti
use -g, but where to insert? If I am trying to use clang++, I have to fix a
lot of things.