Re: [lldb-dev] Discrete code and data memories

2016-05-26 Thread Tyro Software via lldb-dev
org] On Behalf Of Greg > Clayton via lldb-dev > Sent: Wednesday, May 25, 2016 3:57 PM > To: Tyro Software > Cc: lldb-dev@lists.llvm.org > Subject: Re: [lldb-dev] Discrete code and data memories > > I believe that some of the DSPs we have support for (Hexagon?) has this >

Re: [lldb-dev] Discrete code and data memories

2016-05-25 Thread Ted Woodward via lldb-dev
May 25, 2016 3:57 PM To: Tyro Software Cc: lldb-dev@lists.llvm.org Subject: Re: [lldb-dev] Discrete code and data memories I believe that some of the DSPs we have support for (Hexagon?) has this kind of issue. I would speak to Ted Woodward and see if they do anything special for this. Greg Clayton

Re: [lldb-dev] Discrete code and data memories

2016-05-25 Thread Greg Clayton via lldb-dev
I believe that some of the DSPs we have support for (Hexagon?) has this kind of issue. I would speak to Ted Woodward and see if they do anything special for this. Greg Clayton > On May 25, 2016, at 2:16 AM, Tyro Software via lldb-dev > wrote: > > I'm trying to implement LLDB support for an a

[lldb-dev] Discrete code and data memories

2016-05-25 Thread Tyro Software via lldb-dev
I'm trying to implement LLDB support for an architecture where code and data stores can be explicitly separated and can even have overlapping addresses (one can think of it as ROM and RAM, with separate access buses). My impression is that LLDB somewhat presumes a hybrid memory map, e.g. the clien