[lldb-dev] Are overlapping ELF sections problematic?

2019-06-03 Thread Thomas Goodfellow via lldb-dev
I'm working with an embedded platform that segregates memory between executable code, RAM, and constant values. The three kinds occupy three separate address spaces, accessed by specific instructions (e.g. "load from RAM address #0" vs "load from constant ROM address #0") with fairly small ranges f

Re: [lldb-dev] Are overlapping ELF sections problematic?

2019-06-03 Thread Pavel Labath via lldb-dev
On 03/06/2019 10:19, Thomas Goodfellow via lldb-dev wrote: I'm working with an embedded platform that segregates memory between executable code, RAM, and constant values. The three kinds occupy three separate address spaces, accessed by specific instructions (e.g. "load from RAM address #0" vs "l

Re: [lldb-dev] Are overlapping ELF sections problematic?

2019-06-03 Thread Zdenek Prikryl via lldb-dev
Hi Pavel, Thomas, Just a note that this topic is repeating now and then. It'd be nice to have a concept at least. We can go with an additional argument, or enhance addr_t, or enhance Address, or create a new type for it. So, some sort of discussion that would clarify the concept a little bit i