similar to: [LLVMdev] Debug Information Wiki Page

On Nov 5, 2010, at 8:04 AM, Renato Golin wrote: > Hi All, > > We've been working on a wiki page to help people build debug > information in their own front-ends: > > http://wiki.llvm.org/Debug_Information > > It's definitely a work in progress, but it already has the basic > format and how to create the basic information (line, functions, > variables,

On 5 November 2010 22:35, Chris Lattner <clattner at apple.com> wrote: > This looks like great information.  Could it be wrapped up into llvm/docs/SourceLevelDebugging.html instead of put on the wiki page? Hi Chris, It originally was (I still have the source html), but to make it easier for people to contribute, we thought it'd be easier to put on a wiki. Me, Talin and Devag had a

On Nov 6, 2010, at 9:17 AM, Renato Golin wrote: > On 5 November 2010 22:35, Chris Lattner <clattner at apple.com> wrote: >> This looks like great information. Could it be wrapped up into llvm/docs/SourceLevelDebugging.html instead of put on the wiki page? > > Hi Chris, > > It originally was (I still have the source html), but to make it > easier for people to

On 12/03/2010 06:28 PM, Devang Patel wrote: > We are working on a document. Here is current draft: > http://wiki.llvm.org/Debug_Information > > - > Devang While this is great news, it doesn't completely satisfy my needs. Your documentation assumes one is going to use the LLVM provided functions (such as DIFactory::). My front-end can't use them because it is not

Is anyone maintaining this page? http://llvm.org/docs/SourceLevelDebugging.html#composite-type-descriptors DIBuilder::createSubroutineType seems to generate metadatas with a different format. Thanks! Wei -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20130829/70facf50/attachment.html>

On Dec 3, 2010, at 2:39 PM, Bagel wrote: > I am writing a front end for a new language and am having trouble generating > the DWARF debugging information. I'm outputting llvm assembly source so I'm > trying to generate the "!metadata" stuff. > > I have found the document <http://llvm.org/docs/SourceLevelDebugging.html> a > helpful start, as far as it

I am writing a front end for a new language and am having trouble generating the DWARF debugging information. I'm outputting llvm assembly source so I'm trying to generate the "!metadata" stuff. I have found the document <http://llvm.org/docs/SourceLevelDebugging.html> a helpful start, as far as it goes. However, it doesn't quite match what I see clang produce

Hi all, We had some problems in the past when generating debug information, for which I have started a documentation [1]. The recent change to DIBuilder made it more difficult to check for inconsistencies, since neither the original interface nor the current one are documented. This is creating a lot of problems when integrating our front-end to LLVM and we never quite got the debug information

Yes, that is what I was mentioning. (I did not go through all of them.) There are also some minor alignment issues such as - basic, derived, composite type descriptors (second fields) - subprogram descriptor (Function field) -----Original Message----- From: David Blaikie [mailto:dblaikie at gmail.com] Sent: Thursday, August 29, 2013 11:39 AM To: Pan, Wei; Manman Ren Cc: llvmdev at cs.uiuc.edu

On Thu, Aug 29, 2013 at 6:58 AM, Pan, Wei <wei.pan at intel.com> wrote: > Is anyone maintaining this page? ish. We sometimes forget to update it for a while. > http://llvm.org/docs/SourceLevelDebugging.html#composite-type-descriptors > > > > DIBuilder::createSubroutineType seems to generate metadatas with a different > format. composite types recently got one new

On Dec 6, 2011, at 4:13 PM, Devang Patel wrote: > Hi Josh, > > On Dec 4, 2011, at 9:33 PM, Josh Matthews wrote: > >> I'm working on generating debug information for Rust, and I'm >> currently stumped on how to generate DWARF output via LLVM that will >> correctly represent this (eg. when exiting from foo2(), I'd like to >> see "Value returns

Hi Josh, On Dec 4, 2011, at 9:33 PM, Josh Matthews wrote: > I'm working on generating debug information for Rust, and I'm > currently stumped on how to generate DWARF output via LLVM that will > correctly represent this (eg. when exiting from foo2(), I'd like to > see "Value returns is $1 = 5"). I'm generating debug metadata nodes > directly instead of

The Rust compiler defines all functions as returning void, with the first parameter being an outparam of the declared return type, ie. fn foo2() -> int { ret 5; } becomes define void @_ZN4foo217_5cb557d30658848cE(i64*, { i64, { %tydesc*, i1, {} } }*) uwtable { store i64 5, i64* %0 ret void } I'm working on generating debug information for Rust, and I'm currently stumped on how

Unfortunately this is what I'm already doing, and it's not working. I drew inspiration from a disassembly of a program that showed that struct foo { int a; float b; char buf[80]; } struct foo get_foo(void) { foo f = { 5, 2.5 }; return f; } would turn into define void @get_foo(%struct.foo* sret %agg.result) nounwind ssp { ... call void @llvm.memcpy.p0i8.p0i8.i64(i8* %2, i8*

Hello, Do you know where I can find the correct metadata layout in the source code package (which file)? I found a source code that used llvm 2.5 following a slightly different metadata layout as what I read on http://llvm.org/docs/SourceLevelDebugging.html#debugger-intrinsic-functions, which should be compatible with the latest 3.6 version, so where can I check the detailed difference in each

On 4 December 2010 00:28, Devang Patel <dpatel at apple.com> wrote: > We are working on a document. Here is current draft: >        http://wiki.llvm.org/Debug_Information Hi Devang, Do you think we should keep updating the wiki or in the HTML? Do we need this doc to be in the release docs? cheers, --renato

Hello, The documentation for debug information (http://llvm.org/docs/SourceLevelDebugging.html) says the structure of block descriptors metadata is: !3 = metadata !{ i32, ;; Tag = 11 + LLVMDebugVersion (DW_TAG_lexical_block) metadata,;; Reference to context descriptor i32, ;; Line number i32 ;; Column number } However, looking at the generated metadata, there are 2 extra

The debug information is actually still in a different format in the .bc file, it is LLVM metadata. I think the best reference for it is here: https://llvm.org/docs/SourceLevelDebugging.html#ccxx-frontend You can dump it just by disassembling the .bc file to textual IR using llvm-dis and examining the !DI* metadata nodes. You will have to run the file through llc to generate an object file to

> > 3.) Then I used clang-cl to generate a .bc file - but now I'm not able to > use "llvm-readobj" anymore. Is there any tool available which can dump this > debug information too? > ​.bc is LLVM bitcode [1], not the usual object file. `llvm-readobj` should works only on the latter. ​[1] https://llvm.org/docs/BitCodeFormat.html -- Wei-Ren Chen (陳韋任) Homepage:

Hello LLVM-World, I have a question about dumping debug information. 1.) I have compiled an object file with visual studio and debug information. Then I used "llvm-readobj -codeview" and dumped the debug information into a file. This is working great 2.) I used clang-cl for the same task and finally dumped it again with "llvm-readobj". Worked great too. 3.) Then I used