search for: getincludedloc

...or <> on > the #include line, and for the directory it should be the actual header > search path used. > > There are few wrinkles here, because these are preprocessor tokens. > Sure, but I was thinking of nabbing the actual string after macro expansion. Clang's PresumedLoc.getIncludedLoc() points to the post-macro expansion buffer. > - What about #include_next ? > - #include <Foo/Foo.h> does not mean {include path ...}/Foo/Foo.h for > Apple's framework header. > - Some IDEs, like Xcode, uses header maps. If you're curious search > HeaderMaps in clang...

Hi Nick, On Aug 2, 2011, at 6:56 PM, Nick Lewycky wrote: > I've been looking into the debug info in llvm recently. After conferring with a DWARF expert, I think what we really want for a file is to enter the actual name of the header that the preprocessor found between "" or <> on the #include line, and for the directory it should be the actual header search path used.

I've been looking into the debug info in llvm recently. After conferring with a DWARF expert, I think what we really want for a file is to enter the actual name of the header that the preprocessor found between "" or <> on the #include line, and for the directory it should be the actual header search path used. I started by taking a look at how LLVM encodes this in a .s file