Displaying 6 results from an estimated 6 matches for "dbginfoprint".
Did you mean:
dbginfoprinter
2013 Feb 18
1
[LLVMdev] llvm line number of an instruction
...should give full debug information, but I still have the same result. I am aware of http://llvm.org/docs/SourceLevelDebugging.html , from where I can see that is quite easy to take the source line number from a metadata field.
PS: for Allocas, it seems that I have to use findDbgDeclare method from DbgInfoPrinter.cpp.
Thank you in advance !
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20130218/e9c7b4a1/attachment.html>
2009 Jan 14
2
[LLVMdev] Mapping between LLVM bitcode and C source
Hi,
Is there a way, from within an opt pass, to find the correspondence
between an LLVM IR object and C source code (basically line number
info similar to the one used with gcc + gdb to help debugging ),
assuming either a llvm-gcc front end ?
Sorry if this question was asked before.
Thanks for your time.
- Prakash
2009 Jan 29
0
[LLVMdev] Mapping between LLVM bitcode and C source
Same question here!
On Jan 14, 5:14 pm, "Prakash Prabhu" <prakash.pra... at gmail.com> wrote:
> Hi,
>
> Is there a way, from within an opt pass, to find the correspondence
> between an LLVM IR object and Csourcecode(basicallylinenumber
> info similar to the one used with gcc + gdb to help debugging ),
> assuming either a llvm-gcc front end ?
>
> Sorry if
2010 May 18
0
[LLVMdev] DEBUG INFO at the bytecode level
...t; On 05/18/2010 02:13 PM, Zheng Wang wrote:
>> Got it.
>>
>> I am using LLVM 2.6. I guess bool getLocationInfo(const Value *V,
>> std::string &DisplayName,...) has everything I need.\
>
> Yes, for variables.
> For instructions see what printStopPoint() does in DbgInfoPrinter.cpp.
>
> However I'd suggest upgrading to llvm 2.7 and doing your development
> there directly.
> First of all llvm 2.7 has much better debuginfo support (in 2.6 applying
> any optimization would most likely destroy line number debug info)
> Also 2.7 has a new way of represe...
2009 Apr 30
2
[LLVMdev] Pulling line number/file/path information from DbgStopPointInst instructions
Hmm... if I do a print() on the result of getFileName(), I get
i8 * getelementptr ([9 x i8]* @.str, i32 0, i32 0)
back, but if I try to dyn_cast this to GetElementPtrInst it fails
(returning null), so presumably I'm seeing a
GetElementPtrConstantExpr... so how can I get at that constant i8
array without casting to a GetElementPtrInst, and with
GetElementPtrConstantExpr being
2010 May 18
4
[LLVMdev] DEBUG INFO at the bytecode level
Thanks Edwin.
I found DebugInfo.cpp may be useful. Could you tell me which function
I should call inorder to know the source file name and the line number
for a particular instruction?
Cheers,
Zheng
2010/5/18 Török Edwin <edwintorok at gmail.com>:
> On 05/18/2010 01:26 PM, Zheng Wang wrote:
>> Hello,
>>
>> Could I get some debug info at the byte code level? I am