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

2019-06-04 Thread Thomas Goodfellow via lldb-dev
Hi Pavel > I can't say what's the situation in the rest of llvm, but right now lldb > has zero test coverage for the flow you are using, so the fact that this > has worked until now was pretty much an accident. It was a pleasant surprise that it worked at all, since flat memory maps have become n

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

2019-06-04 Thread Thomas Goodfellow via lldb-dev
Hi Zdenek In an ideal world LLVM and LLDB would support a common approach for address spaces. Currently our LLVM backend doesn't yet support address spaces anyway, e.g. access to a variable declared as constant data: const int my_val __attribute__((section (".crom"))) = { 42 }; is only possible

[lldb-dev] June LLVM bay-area social is this Thursday!

2019-06-04 Thread George Burgess IV via lldb-dev
We'll be at Tied House as usual, starting on Thursday the 6th at 7pm! If you can, help us plan and RSVP here: https://www.meetup.com/LLVM-Bay-Area-Social/events/kncsjlyzjbjb/ See everyone there! ___ lldb-dev mailing list lldb-dev@lists.llvm.org https://

[lldb-dev] [Bug 41965] Compile LLDB with coverage results in "LLVM ERROR: out of memory"

2019-06-04 Thread via lldb-dev
https://bugs.llvm.org/show_bug.cgi?id=41965 sguel...@redhat.com changed: What|Removed |Added Resolution|--- |FIXED Status|CONFIRMED