search for: codeview

RFC: CodeView debug info emission in Clang/LLVM Overview On Windows, the de facto debug information format is CodeView, most commonly encountered in the form of a .pdb file. This is the format emitted by the Visual C++, C#, and VB.NET compilers, consumed by the Visual Studio debugger and the Windows debugger (W...

...ymbolFilePDB.h:17: In file included from llvm/DebugInfo/PDB/IPDBSession.h:13: In file included from llvm/DebugInfo/PDB/PDBSymbol.h:13: In file included from llvm/DebugInfo/PDB/ConcreteSymbolEnumerator.h:14: In file included from llvm/DebugInfo/PDB/PDBTypes.h:13: In file included from llvm/DebugInfo/CodeView/CodeView.h:509: llvm/DebugInfo/CodeView/CodeViewRegisters.def:78:13: error: expected identifier CV_REGISTER(CR0, 80) ^ /usr/include/sys/termios.h:184:14: note: expanded from macro 'CR0' #define CR0 0x00000000 ^ In file included from llvm/lldb-...

...blob live in LLVM or Clang for now - the DWARF one at least would probably live in LLVM because type info and other DWARF are described by similar/the same constructs (DIEs, abbrevs, etc) - but it seems like that's not the case for PDB, so there might not be any code to share between LLVM's CodeView needs and the type info construction - then it's just a matter of whether pushing that library down into LLVM for other frontends to use would be good, which it probably will be at some point, so if it goes into Clang I'd at least try to keep it pretty well separated) Potentially that cons...

...d Kleckner <rnk at google.com> wrote: >> >>> On Wed, Mar 21, 2018 at 11:31 AM David Blaikie <dblaikie at gmail.com> >>> wrote: >>> >>>> I'm looking at fixing some layering violations in LLVM & came across a >>>> few in the CodeView handling, specifically: >>>> >>>> lib/MC/MCCodeView includes several llvm/DebugInfo/CodeView headers >>>> I guess MC could be made dependent on DebugInfoCodeView? But probably >>>> these things should be sunk into BinaryFormat as is the case for DWA...

No, Object is supposed to be an abstraction over real object files and LLVM bitcode object files. Maybe we can break the CodeView -> Object dependency. On Thu, Mar 29, 2018 at 4:23 PM Zachary Turner <zturner at google.com> wrote: > It seems a little strange conceptually that object depends on > BitcodeReader. Is it possible to break that dependency? > On Thu, Mar 29, 2018 at 4:11 PM David Blaikie <dblai...

...llvm/DebugInfo/PDB/IPDBSession.h:13: > > In file included from llvm/DebugInfo/PDB/PDBSymbol.h:13: > > In file included from llvm/DebugInfo/PDB/ConcreteSymbolEnumerator.h:14: > > In file included from llvm/DebugInfo/PDB/PDBTypes.h:13: > > In file included from llvm/DebugInfo/CodeView/CodeView.h:509: > > llvm/DebugInfo/CodeView/CodeViewRegisters.def:78:13: error: expected > > identifier > > CV_REGISTER(CR0, 80) > > ^ > > /usr/include/sys/termios.h:184:14: note: expanded from macro 'CR0' > > #define CR0 0x0000000...

On Thu, Mar 22, 2018 at 12:55 PM Reid Kleckner <rnk at google.com> wrote: > On Wed, Mar 21, 2018 at 11:31 AM David Blaikie <dblaikie at gmail.com> wrote: > >> I'm looking at fixing some layering violations in LLVM & came across a >> few in the CodeView handling, specifically: >> >> lib/MC/MCCodeView includes several llvm/DebugInfo/CodeView headers >> I guess MC could be made dependent on DebugInfoCodeView? But probably >> these things should be sunk into BinaryFormat as is the case for DWARF >> features used by MC?...

I've been playing with Fred Riss's "line 0" patch for DWARF (https://reviews.llvm.org/D16569) but in adapting it for current trunk, I find the DwarfDebug stuff has been refactored to allow either DWARF or CodeView. That's all good, but the question is whether the "line 0" patch should be DWARF-specific or common. The DWARF spec explicitly states that code not associated with any particular source location should be associated with line number 0. I don't know what CodeView (or debuggers...

...n file included from llvm/DebugInfo/PDB/IPDBSession.h:13: > In file included from llvm/DebugInfo/PDB/PDBSymbol.h:13: > In file included from llvm/DebugInfo/PDB/ConcreteSymbolEnumerator.h:14: > In file included from llvm/DebugInfo/PDB/PDBTypes.h:13: > In file included from llvm/DebugInfo/CodeView/CodeView.h:509: > llvm/DebugInfo/CodeView/CodeViewRegisters.def:78:13: error: expected > identifier > CV_REGISTER(CR0, 80) > ^ > /usr/include/sys/termios.h:184:14: note: expanded from macro 'CR0' > #define CR0 0x00000000 >...

...22, 2018 at 12:55 PM Reid Kleckner <rnk at google.com> wrote: > >> On Wed, Mar 21, 2018 at 11:31 AM David Blaikie <dblaikie at gmail.com> >> wrote: >> >>> I'm looking at fixing some layering violations in LLVM & came across a >>> few in the CodeView handling, specifically: >>> >>> lib/MC/MCCodeView includes several llvm/DebugInfo/CodeView headers >>> I guess MC could be made dependent on DebugInfoCodeView? But probably >>> these things should be sunk into BinaryFormat as is the case for DWARF >>>...

I'm looking at fixing some layering violations in LLVM & came across a few in the CodeView handling, specifically: lib/MC/MCCodeView includes several llvm/DebugInfo/CodeView headers I guess MC could be made dependent on DebugInfoCodeView? But probably these things should be sunk into BinaryFormat as is the case for DWARF features used by MC? include/llvm/Object/COFF.h includes includ...

Looks like maybe the CodeView -> Object dependency is out of date/old/not needed any more anyway... (don't see any Object headers included from the CodeView headers or implementation, etc). Will see if going that way internally is viable & loop back if it stumbles across something. On Thu, Mar 29, 2018 at 5:27 PM Re...

I mean, we just skip over instructions without a DebugLoc: void CodeViewDebug::beginInstruction(const MachineInstr *MI) { DebugHandlerBase::beginInstruction(MI); // Ignore DBG_VALUE locations and function prologue. if (!Asm || !CurFn || MI->isDebugValue() || MI->getFlag(MachineInstr::FrameSetup)) return; DebugLoc DL = MI->getDebugLoc(); if...

Sounds like we have an issue in the CodeView headers related to a duplicate symbol. While this doesn't entirely surprise me after seeing the error, I'm also not sure why this problem is only just happening now. Ultimately what's happening is we have this enumeration: enum class RegisterId : uint16_t { ... CR3, ... }; But your...

On Wed, Mar 21, 2018 at 11:31 AM David Blaikie <dblaikie at gmail.com> wrote: > I'm looking at fixing some layering violations in LLVM & came across a few > in the CodeView handling, specifically: > > lib/MC/MCCodeView includes several llvm/DebugInfo/CodeView headers > I guess MC could be made dependent on DebugInfoCodeView? But probably > these things should be sunk into BinaryFormat as is the case for DWARF > features used by MC? > I'd be OK...

Hi Mehdi, I understand the reasoning for supporting this proposal independently from CodeView support. However, I do not think that it is needed for supporting CodeView. When I say that my suggestion is more clean, I was pointing to CodeView support, assuming the changes in LLVM IR/Clang FE indicated in this proposal. Also, it is not that clear from the proposal what will be shared (generi...

I also think that we should keep one representation of debug info in the LLVM IR. There would be a need to extend some of the debug info entries to support CodeView, but I think that most of the information generated today by Clang for Dwarf can be used for generating CodeView. I can think about two missing extensions that are needed to CodeView: 1. In Frontend: File Checksum, it is probably a calculation that Clang should do and send to the backend thr...

Hello, LLVM currently supports emission of CodeView's line table subsection. However, we'd like to increase the fidelity of this debug info with column information. I was wondering if anybody had any pointers as to how CodeView represents such information. Thanks! -- David Majnemer -------------- next part -------------- An HTML attachme...

The LLVMCodeView library is definitely independent of the rest of the design questions. As far as testing goes, what would be the conventional LLVM way of testing a library for file format manipulation? A test tool that converts some simple text form into a .obj containing CodeView sections, and comparing with a b...

...e he has trouble expressing CV information entirely in the backend. Regardless of what everyone ends up deciding on with regards to the front-end / back-discussion, I want to suggest separating the work into separate pieces that can go in independently of each other. For example, the proposed LLVMCodeView library, which simply reads and writes raw CV records, seems to be orthogonal to this discussion and could be submitted independently. On Sat, Oct 31, 2015 at 12:04 PM Robinson, Paul via llvm-dev < llvm-dev at lists.llvm.org> wrote: > The details of the mangling would be ABI dependent no...