[Lldb-commits] [PATCH] D40539: Allow using the object file name for debug symbol resolution

Zachary Turner via lldb-commits lldb-commits at lists.llvm.org
Mon Nov 27 22:12:31 PST 2017


yaml2core would be an excellent idea for a tool.

On Mon, Nov 27, 2017 at 9:48 PM Davide Italiano via Phabricator via
lldb-commits <lldb-commits at lists.llvm.org> wrote:

> davide added subscribers: vsk, aprantl, davide.
> davide added a comment.
>
> I thought about this, and it's the only patch from your patchset that I
> don't feel really confident about.
> I'm afraid it's a little risky to add more code to the objectfile reader
> without having proper unittesting.
> In particular, we might want to either check in an object file (not so
> ideal)  or use `llvm-mc` to produce a file with the correct section.
> More generally, when we want to test debug info either we want to
> piggyback on mc or yaml2obj.
> If none of them suffices, we should think about having a tool that takes a
> textual representation of some sort (YAML seems a good start) and produces
> a core dump to be passed to LLDB.
> @sas what do you think?
> cc:ing @vsk / @aprantl for thoughts.
>
>
> https://reviews.llvm.org/D40539
>
>
>
> _______________________________________________
> lldb-commits mailing list
> lldb-commits at lists.llvm.org
> http://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-commits
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.llvm.org/pipermail/lldb-commits/attachments/20171128/e4d6eb5d/attachment.html>


More information about the lldb-commits mailing list