[llvm-dev] Instruction does not dominate all uses!

陳韋任 via llvm-dev llvm-dev at lists.llvm.org
Sat Jun 10 04:54:08 PDT 2017

> I'd use the debugger to call Module::dump after that
>> fault to see where the bitcast really lives. If it's before the alloca
>> (or even not guaranteed to be afterwards) then that's your problem.
> Out of curiosity, do my mean to fire up gdb? Can it call Module:dump()
> after a breakpoint is hit?

Usually you can call dump function in a GDB session, just give it a try.


Wei-Ren Chen (陳韋任)
Homepage: https://people.cs.nctu.edu.tw/~chenwj
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20170610/ef94b94d/attachment.html>

More information about the llvm-dev mailing list