> On Sep 11, 2017, at 10:10 PM, vignesh balu via lldb-dev
> wrote:
>
> Hi All,
>
> I see in the command Mapping Documnet, we can use "image lookup -type" in
> place of "ptype" from gdb. Currently, this can be used only for Type(link
> int, char) , or gloal, static variable or function symbol
> On Sep 11, 2017, at 10:10 PM, vignesh balu via lldb-dev
> wrote:
>
> Hi All,
>
> I see in the command Mapping Documnet, we can use "image lookup -type" in
> place of "ptype" from gdb. Currently, this can be used only for Type(link
> int, char) , or gloal, static variable or function symbol
The original plan was to add a "type eval" to go alongside "type lookup".
"type eval" would take an expression, evaluate it, and then print the resulting
type. gdb's type takes either a type name or an expression, but there's no way
to disambiguate if you have a type that has the same name as
Somebody on stack overflow is reporting:
https://stackoverflow.com/questions/46164427/lldb-is-not-starting-an-application
that they got the 5.0 tools on an Ubuntu system, and lldb is saying:
error: process launch failed: unable to locate lldb-server-5.0.0
when he tries to run a process. The re
Hi,
When deriving RegisterContext_, why some platforms (Arch+OS)
are deriving it from lldb_private::RegisterContext while others are
deriving from lldb_private::RegisterInfoInterface or in other words
how to decide on the base class to derive from between those two and
what are the implications?
