Re: [lldb-dev] RFC: full support for python files, and avoid using FILE* internally

2019-09-24 Thread Lawrence D'Anna via lldb-dev
> On Sep 24, 2019, at 10:04 AM, Ted Woodward wrote: > > A bit of a tangent, but I've been getting requests to debug Python and C++ > together. Things like TensorFlow start in Python, then call into C++ > libraries. Users want to be able to debug the Python code as Python (not > debugging in

Re: [lldb-dev] RFC: full support for python files, and avoid using FILE* internally

2019-09-24 Thread Larry D'Anna via lldb-dev
> On Sep 24, 2019, at 4:11 AM, Pavel Labath wrote: > > On 23/09/2019 20:54, Larry D'Anna wrote: >>> On Sep 23, 2019, at 7:11 AM, Pavel Labath wrote: >>> >>> On 20/09/2019 17:35, Larry D'Anna via lldb-dev wrote: Hi lldb-dev. I want to be able to use LLDB inside of iPython, so I can h

Re: [lldb-dev] Hiding trampoline functions from the backtrace, is it possible ?

2019-09-24 Thread Jim Ingham via lldb-dev
> On Sep 24, 2019, at 11:36 AM, Nat! via lldb-dev > wrote: > > > > On 24.09.19 19:28, Jim Ingham wrote: >> We've had many requests to elide some classes of entries in backtraces - >> like to mirror the Xcode display I mentioned previously. Most of these >> requests don't depend on the fun

Re: [lldb-dev] Hiding trampoline functions from the backtrace, is it possible ?

2019-09-24 Thread Nat! via lldb-dev
On 24.09.19 19:28, Jim Ingham wrote: We've had many requests to elide some classes of entries in backtraces - like to mirror the Xcode display I mentioned previously. Most of these requests don't depend on the functions being marked artificial. So if we're going to do this, something more g

Re: [lldb-dev] Hiding trampoline functions from the backtrace, is it possible ?

2019-09-24 Thread Jim Ingham via lldb-dev
We've had many requests to elide some classes of entries in backtraces - like to mirror the Xcode display I mentioned previously. Most of these requests don't depend on the functions being marked artificial. So if we're going to do this, something more general than just "marked artificial" ->

Re: [lldb-dev] RFC: full support for python files, and avoid using FILE* internally

2019-09-24 Thread Ted Woodward via lldb-dev
A bit of a tangent, but I've been getting requests to debug Python and C++ together. Things like TensorFlow start in Python, then call into C++ libraries. Users want to be able to debug the Python code as Python (not debugging into Python itself), then step into the C++ libraries. They want to g

Re: [lldb-dev] RFC: full support for python files, and avoid using FILE* internally

2019-09-24 Thread Pavel Labath via lldb-dev
On 23/09/2019 20:54, Larry D'Anna wrote: On Sep 23, 2019, at 7:11 AM, Pavel Labath wrote: On 20/09/2019 17:35, Larry D'Anna via lldb-dev wrote: Hi lldb-dev. I want to be able to use LLDB inside of iPython, so I can have mixed python and LLDB debug session. To this end, I’d like to update L

Re: [lldb-dev] Hiding trampoline functions from the backtrace, is it possible ?

2019-09-24 Thread Nat! via lldb-dev
Nat! schrieb am 24.09.19 um 00:28: On 23.09.19 19:22, Adrian Prantl wrote: I think the best mechanism for this would be to ensure that the trampolines are marked up as DW_AT_artificial and/or DW_AT_trampoline by the compiler. I'm pretty sure LLDB then already knows how to hide artificial fra

Re: [lldb-dev] [Release-testers] [9.0.0 Release] Release Candidate 6 is here

2019-09-24 Thread Diana Picus via lldb-dev
Hi, Uploaded f8f3e6bdd640079a140a7ada4eb6f5f05aeae125cf54b94d44f733b0e8691dc2 clang+llvm-9.0.0-aarch64-linux-gnu.tar.xz ff6046bf98dbc85d7cb0c3c70456bc002b99a809bfc115657db2683ba61752ec clang+llvm-9.0.0-armv7a-linux-gnueabihf.tar.xz Cheers, Diana On Thu, 19 Sep 2019 at 16:56, Hans Wennborg via Re