On 11/10/20 10:01 PM, Jonas Devlieghere wrote:
On Nov 10, 2020, at 12:58 PM, Zdenek Prikryl wrote:
Hi all,
Just for the record, we have successfully implemented the wrapping of addr_t
into a class to support multiple address spaces. The info about address space
is stored in the ELF file, so
Are these the use cases you were envisioning, Jonas?
>>
>>> -----Original Message-----
>>> From: lldb-dev On Behalf Of Pavel Labath
>>> via lldb-dev
>>> Sent: Tuesday, October 20, 2020 12:51 PM
>>> To: Jonas Devlieghere ; LLDB >> d...@lists.llvm.o
can give the user the flexibility to pick how
to view memory.
Are these the use cases you were envisioning, Jonas?
-Original Message-
From: lldb-dev On Behalf Of Pavel Labath
via lldb-dev
Sent: Tuesday, October 20, 2020 12:51 PM
To: Jonas Devlieghere ; LLDB
Subject: [EXT] Re: [lldb-
On 22/10/2020 10:25, Jason Molenda wrote:
Hi Greg, Pavel.
I think it's worth saying that this is very early in this project. We know
we're going to need the ability to track segments on addresses, but honestly a
lot of the finer details aren't clear yet. It's such a fundamental change that
> On Oct 22, 2020, at 1:25 AM, Jason Molenda wrote:
>
> Hi Greg, Pavel.
>
> I think it's worth saying that this is very early in this project. We know
> we're going to need the ability to track segments on addresses, but honestly
> a lot of the finer details aren't clear yet. It's such a f
Hi Greg, Pavel.
I think it's worth saying that this is very early in this project. We know
we're going to need the ability to track segments on addresses, but honestly a
lot of the finer details aren't clear yet. It's such a fundamental change that
we wanted to start a discussion, even though
give the user the flexibility to pick how to view memory.
Are these the use cases you were envisioning, Jonas?
> -Original Message-
> From: lldb-dev On Behalf Of Pavel Labath
> via lldb-dev
> Sent: Tuesday, October 20, 2020 12:51 PM
> To: Jonas Devlieghere ; LLDB d..
There's a lot of things that are unclear to me about this proposal. The
mechanics of representing an segmented address are one thing, but I I
think that the really interesting part will be the interaction with the
rest of lldb. Like
- What's going to be the source of this address space informati
> On Oct 19, 2020, at 2:56 PM, Jonas Devlieghere via lldb-dev
> wrote:
>
> We want to support segmented address spaces in LLDB. Currently, all of LLDB’s
> external API, command line interface, and internals assume that an address in
> memory can be addressed unambiguously as an addr_t (aka u
