search for: pdbdump

Hi, This might be interesting since it seems to be the only LLVM test failing with VS 2015: FAIL: LLVM :: DebugInfo/PDB/pdbdump-symbol-format.test (7377 of 14212) ******************** TEST 'LLVM :: DebugInfo/PDB/pdbdump-symbol-format.test' FAILED ******************** Script: -- llvm-pdbdump -symbols C:\cygwin64\home\ismail\src\llvm\test\DebugInfo\PDB/Inputs/symbolformat.pdb | C:/cygwin64/home/ismail/ src/llvm/dist/....

...succeeded, 0 failed, 266 up-to-date, 0 skipped ========== ~Aaron On Tue, Jul 21, 2015 at 8:50 AM, İsmail Dönmez <ismail at donmez.ws> wrote: > Hi, > > This might be interesting since it seems to be the only LLVM test > failing with VS 2015: > > FAIL: LLVM :: DebugInfo/PDB/pdbdump-symbol-format.test (7377 of 14212) > ******************** TEST 'LLVM :: > DebugInfo/PDB/pdbdump-symbol-format.test' FAILED ******************** > Script: > -- > llvm-pdbdump -symbols > C:\cygwin64\home\ismail\src\llvm\test\DebugInfo\PDB/Inputs/symbolformat.pdb > | C:/cy...

...NABLE_TIMESTAMPS=ON -DLLVM_ENABLE_ASSERTIONS=ON -DLLVM_INSTALL_TOOLCHAIN_ONLY=ON -DLLVM_TARGETS_TO_BUILD="ARM;X86" -DPYTHON_EXECUTABLE=$python_exe -DLLVM_BUILD_TESTS=ON -DLLVM_LIT_TOOLS_DIR=C:/cygwin64/bin fwiw compiler-rt is also enabled. Also if you can forward me the output of llvm-pdbdump.exe -types llvm/test/DebugInfo/PDB/Inputs/symbolformat.pdb then I can compare the outputs. Thanks! On Tue, Jul 21, 2015 at 5:27 PM, Aaron Ballman <aaron at aaronballman.com> wrote: > FWIW, this test is passing for me on Windows 7 with Visual Studio 2015 > (debug build). > > 59...

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

...t; defines macros named min and max in conflict with >> <algorithm>. Prevent macro expansion by wrapping std::min in >> parenthesis. >> > > Could we just build with NOMINMAX in the windows build? > > >> >> Modified: >> llvm/trunk/tools/llvm-pdbdump/llvm-pdbdump.cpp >> >> Modified: llvm/trunk/tools/llvm-pdbdump/llvm-pdbdump.cpp >> URL: >> http://llvm.org/viewvc/llvm-project/llvm/trunk/tools/llvm-pdbdump/llvm-pdbdump.cpp?rev=250383&r1=250382&r2=250383&view=diff >> >> ==============================...

I submitted this yesterday in r274171. I think this allows for a more intuitive way to structure the options of command line tools. It's optional and if you do nothing llvm::cl will work as it always has for you. Probably self explanatory, but here's some output of --help from llvm-pdbdump, which was updated to use subcommands in r274247, in case anyone wants to see what this looks like. D:\src\llvmbuild\clang-selfhost>bin\llvm-pdbdump --help OVERVIEW: LLVM PDB Dumper USAGE: llvm-pdbdump.exe [subcommand] [options] SUBCOMMANDS: pdb2yaml - Generate a detailed YAML description...

...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 info from > the file. > > It's pretty complete for reading pdb files, and I'm actively working on > expanding write support. I'll check into that again. I ran across llvm-pdbdump earlier...

I came across a PDB that caused llvm-pdbdump to crash. I tracked it down to a missing overload for a data type in the variable printer. When I tried to provide an implementation, I discovered that there were some bugs in the existing overloads and it was easy to come up with combinations of types that weren't being dumped right. I crea...

...iltz, Denis <Denis.Briltz at intel.com> > wrote: > > Hi, > > > > “clang-x64-ninja-win7” was switched to VS2015. > > > > It is red now due to a few PDB tests and one sanitizer test. > > > > Failing Tests (10): > > LLVM :: DebugInfo/PDB/DIA/pdbdump-flags.test > > LLVM :: DebugInfo/PDB/DIA/pdbdump-linenumbers.test > > LLVM :: DebugInfo/PDB/DIA/pdbdump-symbol-format.test > > LLVM :: tools/llvm-pdbdump/class-layout.test > > LLVM :: tools/llvm-pdbdump/enum-layout.test > > LLVM :: tools/llvm-pdbdum...

The new error message is: llvm-pdbdump: DIA Error: An unknown error has occurred. HRESULT: 0x800700C1: Calling NoRegCoCreate which is more or less what I expected. The specific HResult is kind of interesting, it maps to "msdia140.dll is not a valid Win32 application". I don't know if this means that it can't find t...

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...

Hi, “clang-x64-ninja-win7” was switched to VS2015. It is red now due to a few PDB tests and one sanitizer test. Failing Tests (10): LLVM :: DebugInfo/PDB/DIA/pdbdump-flags.test LLVM :: DebugInfo/PDB/DIA/pdbdump-linenumbers.test LLVM :: DebugInfo/PDB/DIA/pdbdump-symbol-format.test LLVM :: tools/llvm-pdbdump/class-layout.test LLVM :: tools/llvm-pdbdump/enum-layout.test LLVM :: tools/llvm-pdbdump/load-address.test LLVM :: tools/llvm-pdbdump...

...hich has been checked in and currently has limited support for dumping pdb. There's still more to be done on the 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....

Is making PDB files for corresponding IR supported in LLVM latest version? After some searching I see llvm-pdbdump, but I want to annotate the IR with debug information so that when I write bitcode it has pdb information. I've heard of CodeView, but it seems to be only for line information. I want variable values also. I would be ok to use DWARF if Visual Studio could understand it using LLDB but I don...

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

Hi All, As a part of a recent move of libFuzzer from LLVM to compiler-rt I am looking into updating the build code for the libraries which use libFuzzer. I have looked into tools/llvm-pdbutil, and “ninja llvm-pdbutil-fuzzer” does not build at all, and the error refers to non-existent headers. The last update to the codebase is reasonably recent, and was done in June 2017. Is anyone using it?

...llvm command line tools. This potentially has broad interest (either positive or negative), so I figured I'd give a heads up here instead of just on llvm-commits. The motivation for this is that we frequently have tools with incompatible sets of command line options. I ran into this on llvm-pdbdump and was debating breaking off some of the functionality into a separate tool to make the command line interface more sensible, and to prevent people getting confused about which options could be used with which other options. A better approach to this, in my opinion, is the use of sub commands. T...

What makes the reports not actionable on windows? On Tue., 22 Aug. 2017, 3:49 pm Reid Kleckner via llvm-dev < llvm-dev at lists.llvm.org> wrote: > I think we should delete it. David implemented it a long time ago when he > was working on llvm-pdbdump, but he's moved on. Zach was never able to use > it effectively because he works on Windows, so the reports were not > actionable. > > On Tue, Aug 22, 2017 at 2:45 PM, George Karpenkov <ekarpenkov at apple.com> > wrote: > >> Hi All, >> >> As a part of a...

...It turns out I was running CMake without the VS Environment vars set, so %VSINSTALLDIR% was empty. Running with the environment set up correctly fixed the problem. On Tue, Jul 26, 2016 at 7:56 PM, Zachary Turner <zturner at google.com> wrote: > Even if you don't have DIA SDK, llvm-pdbdump will still work with the > "raw" subcommand, just not the "pretty" subcommand. > I was running a 3.8 install where this functionality had apparently not yet landed. I pulled a fresh install from trunk earlier and I'm now playing around with "raw". So far thi...

...and currently has limited support for dumping pdb. > > There's still more to be done on the 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 ca...