search for: lldm

Hi, I have a question about using lldm-db. I compiled a simple program using "llvmgcc -g" and loaded the resulting .bc file into llvm-db, but when I tried to set a breakpoint by "b main", it complained "Error: Program contains no debugging information!". Is there anything obvious that I did wrong here? What...

...ent. So my question is whether: - The above addition to the IR is the correct thing to do [but if so then there is possibly a further issue in SelectionDAGBuilder::visitIntrinsicCall()'s handling of this additional line (where it is currently being discarded)] - Some other @lldm.dbg.value entry should be produced to generate the correct debug information. Keith -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20160729/baaf3dc2/attachment.html>

...er: > > - The above addition to the IR is the correct thing to do [but > if so then there is possibly a further issue in > SelectionDAGBuilder::visitIntrinsicCall()’s handling of this additional > line (where it is currently being discarded)] > > - Some other @lldm.dbg.value entry should be produced to > generate the correct debug information. > > > > Keith > _______________________________________________ > LLVM Developers mailing list > llvm-dev at lists.llvm.org > http://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-dev > -----...

The main goal of these patch series is to implement a new API that allows to retrieve created device-mapper devices for volumes and partitions back after they have been created. As part of this patch: - required libdevmapper version was bumped to 1.02. I think it is safe because it was released more then 10 years ago; - newer version of libdevmapper allowed to simplify code base a little bit; -