search for: cv2pdb

...ave some ability to convert to PDB, though it >>> looks like the project stalled years ago... >>> >>> http://www.dsource.org/projects/visuald >>> >> >> Years ago? Latest release was only 2 months ago. >> > > My mistake, I was referring to cv2pdb which according the the web-page > last had news in 2006. I had not looked in a few years. According to the > repository, the project has not had a commit in three years. > He recently added DWARF support, and serviced a couple of feature requests for me, so it's still alive. I'm...

...uce COFF files with embedded DWARF >> debug relatively easily, which produces executables debuggable via the >> MinGW tool-chain. >> > > This sounds effectively identical to what I have now using MinGW GCC to > produce COFF binaries with DWARF debug info, and then running cv2pdb after > linking to extract a PDB from the binary. It works, but it means I can't > link against MSVC libs/objects because of the conflicting debug info > formats. :/ > > > To support another debug format would be difficult I think, though I'm no >> expert on the subj...

...though it >>>> looks like the project stalled years ago... >>>> >>>> http://www.dsource.org/projects/visuald >>>> >>> >>> Years ago? Latest release was only 2 months ago. >>> >> >> My mistake, I was referring to cv2pdb which according the the web-page >> last had news in 2006. I had not looked in a few years. According to the >> repository, the project has not had a commit in three years. >> > > He recently added DWARF support, and serviced a couple of feature requests > for me, so it...

Hi people, Unlike GCC, LLVM has seemingly good support for interoperability with MSVC built windows code. This makes LLVM particularly attractive to my company/project, but it seems LLVM doesn't support writing PDB debug into into it's COFF output. It seems Win64 exception handling has been added recently, which perhaps makes PDB the only outstanding feature for effective use with

...able to get clang to produce COFF files with embedded DWARF > debug relatively easily, which produces executables debuggable via the > MinGW tool-chain. > This sounds effectively identical to what I have now using MinGW GCC to produce COFF binaries with DWARF debug info, and then running cv2pdb after linking to extract a PDB from the binary. It works, but it means I can't link against MSVC libs/objects because of the conflicting debug info formats. :/ To support another debug format would be difficult I think, though I'm no > expert on the subject. Currently LLVM internally r...

...merging my PDBs. > In my case, what I do with my team and try to achieve is this : > - Run our application under a visual studio debugger > - Generate JIT code ( using llvm MCJIT ) > - Then, either : > - export as COFF obj file with dwarf information and then convert it > with cv2pdb to obtain a pdb of my JIT symbols (what I do now) > - export directly to PDB my JIT debug info (what i would like to do, if > you have an idea how..) > - Detach the visual studio debugger > - Merge my JIT pdb into a copy of the executable pdb (where things start > to go bad..) &gt...

...do with my team and try to achieve is this : >>> - Run our application under a visual studio debugger >>> - Generate JIT code ( using llvm MCJIT ) >>> - Then, either : >>> - export as COFF obj file with dwarf information and then convert it >>> with cv2pdb to obtain a pdb of my JIT symbols (what I do now) >>> - export directly to PDB my JIT debug info (what i would like to do, >>> if you have an idea how..) >>> - Detach the visual studio debugger >>> - Merge my JIT pdb into a copy of the executable pdb (where th...

...his : >>>>> - Run our application under a visual studio debugger >>>>> - Generate JIT code ( using llvm MCJIT ) >>>>> - Then, either : >>>>> - export as COFF obj file with dwarf information and then convert >>>>> it with cv2pdb to obtain a pdb of my JIT symbols (what I do now) >>>>> - export directly to PDB my JIT debug info (what i would like to >>>>> do, if you have an idea how..) >>>>> - Detach the visual studio debugger >>>>> - Merge my JIT pdb into a copy...

...our application under a visual studio debugger >>>>>>> - Generate JIT code ( using llvm MCJIT ) >>>>>>> - Then, either : >>>>>>> - export as COFF obj file with dwarf information and then convert >>>>>>> it with cv2pdb to obtain a pdb of my JIT symbols (what I do now) >>>>>>> - export directly to PDB my JIT debug info (what i would like to >>>>>>> do, if you have an idea how..) >>>>>>> - Detach the visual studio debugger >>>>>>&gt...

...studio debugger >>>>>>>>> - Generate JIT code ( using llvm MCJIT ) >>>>>>>>> - Then, either : >>>>>>>>> - export as COFF obj file with dwarf information and then >>>>>>>>> convert it with cv2pdb to obtain a pdb of my JIT symbols (what I do now) >>>>>>>>> - export directly to PDB my JIT debug info (what i would like >>>>>>>>> to do, if you have an idea how..) >>>>>>>>> - Detach the visual studio debugger &gt...

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

...>>>>>>> - Generate JIT code ( using llvm MCJIT ) >>>>>>>>>>> - Then, either : >>>>>>>>>>> - export as COFF obj file with dwarf information and then >>>>>>>>>>> convert it with cv2pdb to obtain a pdb of my JIT symbols (what I do now) >>>>>>>>>>> - export directly to PDB my JIT debug info (what i would like >>>>>>>>>>> to do, if you have an idea how..) >>>>>>>>>>> - Detach the vi...

...> - Generate JIT code ( using llvm MCJIT ) >>>>>>>>>>>>> - Then, either : >>>>>>>>>>>>> - export as COFF obj file with dwarf information and then >>>>>>>>>>>>> convert it with cv2pdb to obtain a pdb of my JIT symbols (what I do now) >>>>>>>>>>>>> - export directly to PDB my JIT debug info (what i would >>>>>>>>>>>>> like to do, if you have an idea how..) >>>>>>>>>>>...

...gt; - Then, either : >>>>>>>>>>>>>>>>>>>>>>>>> - export as COFF obj file with dwarf >>>>>>>>>>>>>>>>>>>>>>>>> information and then convert it with cv2pdb to obtain a pdb of my JIT >>>>>>>>>>>>>>>>>>>>>>>>> symbols (what I do now) >>>>>>>>>>>>>>>>>>>>>>>>> - export directly to PDB my JIT debug info &...

...er : >>>>>>>>>>>>>>>>>>>>>>>>>>> - export as COFF obj file with dwarf >>>>>>>>>>>>>>>>>>>>>>>>>>> information and then convert it with cv2pdb to obtain a pdb of my JIT >>>>>>>>>>>>>>>>>>>>>>>>>>> symbols (what I do now) >>>>>>>>>>>>>>>>>>>>>>>>>>> - export directly to PDB my...