Stefan Kratochwil wrote:
> [...]
> I am developing a dynamic software updating tool for dynamically
> linked C libraries (in short: I want to patch dynamic libraries
> in-memory).
See also dyninst.
> [...]
> I am currently unaware of what types of information I _really_ need,
> so for now, gett
> On Oct 30, 2015, at 3:35 AM, Stefan Kratochwil via lldb-dev
> wrote:
>
> Hi Greg,
>
> thanks for your reply.
>
> I am developing a dynamic software updating tool for dynamically linked C
> libraries (in short: I want to patch dynamic libraries in-memory).
>
> My goal is to achieve that wi
Hi Greg,
thanks for your reply.
I am developing a dynamic software updating tool for dynamically linked
C libraries (in short: I want to patch dynamic libraries in-memory).
My goal is to achieve that without any code instrumentation. The main
problem is the state transformation between the o
> On Oct 13, 2015, at 2:42 AM, Stefan Kratochwil via lldb-dev
> wrote:
>
> Hi altogether,
>
> I currently am developing an application where I need to access the DWARF
> debugging information of my target process and its loaded .so files.
>
> In more detail, I need to match type information
> On Oct 13, 2015, at 9:03 AM, Stefan Kratochwil via lldb-dev
> wrote:
>
> Hi,
>
> well, I found the llvm-dwarfdump tool in the tools directory *facepalm*...
> I'll use that as a reference.
>
> That leaves the question about the two separate DWARF implementations.
Ideally it would be good to
Hi,
well, I found the llvm-dwarfdump tool in the tools directory *facepalm*...
I'll use that as a reference.
That leaves the question about the two separate DWARF implementations.
Cheers,
Stefan
On 10/13/2015 11:42 AM, Stefan Kratochwil via lldb-dev wrote:
Hi altogether,
I currently am devel
