[llvm-dev] [PDB] [JIT] Write to PDB file when COFFObjectFile is emitted by JIT

[Rui Ueyama via llvm-dev]

I'm sorry but I don't think I understand the question. But if you can't
produce a pdb using MSVC, it is hard to imagine that only lld can do,
unless MSVC linker has a bug.


On Wed, Mar 14, 2018 at 3:07 PM Vivien Millet <vivien.millet at gmail.com>
wrote:

> Hi, thanks for the answers, i tried to use LINK.EXE to produce a pdb, but
> unfortunately, it produces an empty pdb (i have debug symbols in the dumped
> .obj because I can see them with PEViewer).
> It is probably because i have undefined symbols, which is logical because
> i'm dumping machine code which points to running native code. I still dont
> understand why LINK.EXE is not able to produce a valid pdb for my valid
> symbols even if all symbols referenced are not resolved.
> Do you think LLD would do the same if the .obj is not 'valid' by itself
> alone ?
>
> 2018-03-14 22:07 GMT+01:00 Rui Ueyama <ruiu at google.com>:
>
>> On Fri, Mar 9, 2018 at 7:00 PM Lang Hames <lhames at gmail.com> wrote:
>>
>>> Hi Vivien,
>>>
>>> I'm not familiar with Windows development, but I believe you could dump
>>> the object file to disk then run LINK.EXE to produce the PDB.
>>> Alternatively, I think LLD can also produce PDB files (Rui -- is that
>>> right?), in which case you may be able to use that.
>>>
>>
>> Yes, lld can produce PDB files.
>>
>>
>>> Is the aim to be able to debug JIT'd code? Which debugger do you plan to
>>> use?
>>>
>>> -- Lang.
>>>
>>>
>>> On Thu, Mar 8, 2018 at 4:23 AM, Vivien Millet via llvm-dev <
>>> llvm-dev at lists.llvm.org> wrote:
>>>
>>>> Is it possible to write a .pdb file containing the debug info stored in
>>>> a COFFObjectFile once the NotifyObjectEmitted is triggered by the JIT
>>>> compiler ?
>>>>
>>>> _______________________________________________
>>>> LLVM Developers mailing list
>>>> llvm-dev at lists.llvm.org
>>>> http://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-dev
>>>>
>>>>
>>>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20180314/167b833c/attachment.html>