Re: [lldb-dev] lldb_private::RegisterContext vs lldb_private::RegisterInfoInterface

Sorry, I could not respond yesterday as I was of out of office. > Interesting. There are two ways to accomplish this: > 1 - Treat the CPU as one target and the GPU as another. > 2 - Treat the CPU and GPU as one target > > The tricky things with solution #1 is how to manage switching the targets >

Re: [lldb-dev] lldb_private::RegisterContext vs lldb_private::RegisterInfoInterface

> On Sep 21, 2017, at 5:15 AM, Ramana wrote: > > Sorry, I could not respond yesterday as I was of out of office. > >> Interesting. There are two ways to accomplish this: >> 1 - Treat the CPU as one target and the GPU as another. >> 2 - Treat the CPU and GPU as one target >> >> The tricky thing

Re: [lldb-dev] lldb_private::RegisterContext vs lldb_private::RegisterInfoInterface

We've done something similar in-house running on a Snapdragon with an ARM and a Hexagon DSP. We use Android Studio to debug an app on the ARM that sends work down to the Hexagon, running an app under Linux. On the Hexagon we ran lldb, and were able to debug both apps talking to each other. -- Q

[lldb-dev] IMPORTANT: *.llvm.org certificates being renewed (impacts SVN) FRIDAY Sept 22

All, The following llvm.org certificates will be renewed tomorrow, Friday Sept 22nd at ~7:30AM PDT. bugs.llvm.org clang-analyzer.llvm.org clang.llvm.org compiler-rt.llvm.org