search for: pdbs

On Tue, Jul 26, 2016 at 8:02 AM, Reid Kleckner <rnk at google.com> wrote: > We've been pursuing the direction of writing PDBs from scratch in > llvm/lib/DebugInfo/PDB/Raw and related directories. It might be interesting > to have code that talks to MSPDB140.dll in LLVM, but we really want LLD to > be able to produce its output on any platform. > I completely agree about independence from arbitrary platform-...

Hi Zach (or anyone else who may have a clue), I'm currently investigating making use of LLVM for PDB parsing for with a view to supporting partial PDBs as produced by /DEBUG:FASTLINK as the VS DIA SDK hasn't been updated to handle them. I know this is probably low on your priority list but since /DEBUG:FASTLINK is now the implied default for VS2017 I figure it's a good time to take a look at it. Unfortunately I'm finding very little i...

On Thu, Oct 29, 2015 at 12:42 PM, Daniel Dilts via cfe-dev < cfe-dev at lists.llvm.org> wrote: > 2. Will LLD and LLDB be updated as necessary to support CodeView? > Rui is is looking at making LLD link codeview from object files into PDBs. Zachary Turner intends to add PDB reading support to LLDB. We already have a PDB implementation of DIContext in lib/DebugInfo that uses PDBs. The only client is currently llvm-symbolizer, but the idea was that LLDB could use it, and eventually we should shift it off DIA and over to something cros...

Hi all, I've recently been doing some work on a novel language that uses LLVM for optimization and machine codegen. The language is self-hosted, I'm building my third iteration of its garbage collector, and also writing a thin IDE to stretch the language a bit. Needless to say, debugging is a major concern for me. My primary experience (and primary development focus) is Windows-centric,

On Wed, Jul 27, 2016 at 12:06 AM, Johan Wehrli <johan.wehrli at strong.codes> wrote: > > Most of the time, it is a path problem: > https://support.microsoft.com/en-us/kb/3035999 > > If you open the file cmake/config-ix.cmake you will find the place where > cmake check if the DIA_SDK is present (there is also a note saying that > sometime this is a Windows bug). > >

Hi Mike, > I'll check into that again. I ran across llvm-pdbdump earlier but couldn't get it to build on a vanilla 3.8 install (CMake is convinced I don't have the DIA SDK and I haven't found a way to change its mind). I have experienced something similar with the DIA SDK. Most of the time, it is a path problem: https://support.microsoft.com/en-us/kb/3035999

Yes I am the person who wrote this feature (along with most other PDB-related features). I thought about some and I think it's a bit hard (if not impossible) to merge PDBs in this way. Here's a short list of things I came up with 1) We need to merge the list of modules. This requires first detecting if two modules are actually the same. For example, if I run llvm-pdbutil on a random PDB on my disk, I get this (output is trimmed for brevity) $ llvm-pdbutil.ex...

Hello, I'm trying to parse debug information out of PDB files that's created by visual studio, and also maybe producing stacktrace on linux. Does anyone has leads to how I can do that with LLVM's pdbutil? Or point me to a documentation about that? Thanks. Experian -------------- next part -------------- An HTML attachment was scrubbed... URL:

...me. We could probably hide the subcommand so users don’t accidentally use it, or if someone wants to properly implement the missing features, that would be even better On Sat, Dec 22, 2018 at 10:48 AM Vivien Millet via llvm-dev < llvm-dev at lists.llvm.org> wrote: > When trying to merge 2 pdbs which have each their own DBI stream, I endup > with a pdb with an inconsistent number of stream and no DBI stream (or at > least not at fixed index 3, producing a corrupt error when dumping with -l). > Looking at the code, it seems that we don't merge other streams than TPI > and I...

On Tue, Jul 26, 2016 at 12:30 PM, Zachary Turner <zturner at google.com> wrote: > I wrote most of the pdb code in llvm so far. As Reid suggested, if you > look in DebugInfo/PDB/Raw there is a significant amount of code dealing > with msf files and raw pdb streams. If you build the llvm-pdbdump tool you > can run it with the "raw" subcommand to dump lots of low level

...LVM's PDB APIs should (hopefully) be fairly self-explanatory and you can read the code of llvm-pdbutil to see how it does various things, which you can copy. On Wed, May 15, 2019 at 4:35 PM Reid Kleckner <rnk at google.com> wrote: > I would say that llvm-pdbutil mainly exists to dump PDBs as human readable > text, and to translate them to and from YAML. As far as interpreting the > contents of the PDB to do something useful, like produce a stack trace, > goes, the consumer of LLVM's PDB reading libraries is responsible for doing > that. For example, LLDB at some poin...

...lelization inside of addObjectsToPDB Is anyone working on those? Also has anyone thought about merging .obj files to deduplicate type infomation so we can do the linking on projects to generate something like a lib file, but deduplicated debug information (as far as I know actual .lib just put all pdbs or /Z7 debug info inside a file without dedup). Just looking at the code it seems it is much more mature and also the choice of SHA1_8 seems interesting (still don't know why not use xxHash64). ps: My code to add ghashes to msvc compiled .obj files is almost ready to be pushed as an option fo...

When trying to merge 2 pdbs which have each their own DBI stream, I endup with a pdb with an inconsistent number of stream and no DBI stream (or at least not at fixed index 3, producing a corrupt error when dumping with -l). Looking at the code, it seems that we don't merge other streams than TPI and IPI streams, am I rig...

...pdb dumping tool, but at this point -- to reduce duplicated effort -- I think it makes the most sense to start moving some of this logic into a library in llvm, and then change llvm-pdbdump to use the library. Later, once the library is more comprehensive, I plan to then use it in LLDB for reading PDBs while debugging on Windows. I think the best way to do this is to move all of the code in lib/DebugInfo to lib/DebugInfo/dwarf, and then make another folder called lib/DebugInfo/pdb. These would then be compiled into two separate libraries. Another approach is to just put the PDB code in the sa...

Hello, Is anyone working on implementing DebugInfo/PDB that doesn't depend on DIA? What would it take to have minimal implementation that would allow to take a PDB file and look up symbols using llvm-symbolizer on a non-Windows (e.g. Linux or MacOS) platform? Regards, Dmitri -------------- next part -------------- An HTML attachment was scrubbed... URL:

Hi, I'm using IR and MCJIT to compile a script language. I debug it with on the fly generated .pdb files. During debugging, almost each time I step into a function, I loose information about calling function inside the visual studio callstack view or I have a bunch of pure addresses in the callstack in between the current function and the calling function, for example :

...for deeply nested or complex types. Did anyone else have the same problems, or any way to try to figure out what is missing? I tried llvm-pdbutil dump -symbols but there is a lot of small diferences on pdb's generated by taking msvc C7 debug information and linking with lld and msvc generating pdbs and linking with link.exe so its hard to see any big parts missing. -- Leonardo Santagada

...uliaLang, in our debuginfo.cpp file), by setting the no-frame-pointer-optim flag in the IR, then creating and populating a dummy unwind description object in the .text section, and registering that dynamically. Some day I hope to actually just register the .pdata/.xdata sections with the unwinder. PDBs are a bit different though, since the above steps work well for gdb, but generally I find that WinDbg is less willing or able to be given JIT-frame information from LLVM. (I assume somehow it can be done, for dotNET. I just don't know how.) On Sat, Feb 29, 2020 at 11:07 PM Reid Kleckner via ll...

...s Meow Hash (uses hardware AES SSE 4.2 instructions), which brings the figures down a bit. Future changes could write back the computed ghash stream back to OBJs if /INCREMENTAL is specified (just an idea). Incrementally linking will be faster that way when working with MSVC OBJs. As for creating PDBs for independent projects, that would help most likely. However the ghash stream would need to be stored in the PDB in that case (currently, ghashes are dropped after merging). That could help when using rarely compiled projects, used along with network caches. I will start sending smaller patches...

....hasArgNoClaim(OPT_INPUT)) { fixupExports(); createImportLibrary(/*AsLib=*/true); - exit(0); + return; } // Handle /delayload @@ -1122,7 +1122,7 @@ void LinkerDriver::link(ArrayRef<const char *> ArgsArr) { // This is useful because MSVC link.exe can generate complete PDBs. if (Args.hasArg(OPT_msvclto)) { invokeMSVC(Args); - exit(0); + return; } // Do LTO by compiling bitcode input files to a set of native COFF files then @@ -1173,8 +1173,7 @@ void LinkerDriver::link(ArrayRef<const char *> ArgsArr) { // Write the result. writeResult(&...