[Lldb-commits] [PATCH] D116211: With firmware debug sess, if gdb stub knows the UUID/address of binary, try to load it

Pavel Labath via Phabricator via lldb-commits lldb-commits at lists.llvm.org
Tue Jan 4 05:42:18 PST 2022


labath added a comment.

In D116211#3218911 <https://reviews.llvm.org/D116211#3218911>, @jasonmolenda wrote:

> In D116211#3211319 <https://reviews.llvm.org/D116211#3211319>, @labath wrote:
>
>> What happened to the test case?
>
> I didn't think of a way of constructing one very easily with what we have r.n. :/  The closest would be a gdb_remote_client test, but we need a binary that the gdb server can reply with the UUID of.

Yes, that's pretty much what I had in mind. You can use yaml2obj to construct a binary with a well-known uuid. We already have a couple of gdb-client tests using yaml2obj. The easiest way to create one is to use obj2yaml on an existing (small) binary and then (possibly) delete the uninteresting stuff in an editor.


Repository:
  rG LLVM Github Monorepo

CHANGES SINCE LAST ACTION
  https://reviews.llvm.org/D116211/new/

https://reviews.llvm.org/D116211



More information about the lldb-commits mailing list