Hello,
It's been a while since I asked this question on the mailing list ( 2~ years
ago).
I am interested in what would be the current best way for implementing
interleaved / mixed-mode Python backtraces when debugging the CPython
interpreter.
So if I run lldb -- python /path/to/my/script, se
Not strictly related to LLDB but you might find this interesting:
https://blogs.dropbox.com/tech/2018/11/crash-reporting-in-desktop-python-applications
On Tue, Nov 20, 2018 at 8:51 AM Alexandru Croitor via lldb-dev <
lldb-dev@lists.llvm.org> wrote:
> Hello,
>
> It's been a while since I asked th
On Tue, Nov 20, 2018 at 8:51 AM Alexandru Croitor via lldb-dev <
lldb-dev@lists.llvm.org> wrote:
>
> I would appreciate, if someone could point me to some relevant code that
> does something similar to what I'm asking, so I could use it as a base
> point for exploration.
>
> Many thanks.
Not sur
Thanks. That's useful info that covers the "squishing" of C frames into Python
frames.
The link to the slides at the end also mentions two other useful projects for
walking the stack, py-spy and pyflame.
Having said that, I'm more interested on the "lldb" side of things.
On 20. Nov 2018, at 18
Thanks for the link. I'm aware that VS provides that functionality (although I
forgot that it was open-source).
My aim would be to implement something similar in LLDB though.
On 20. Nov 2018, at 18:49, Zachary Turner
mailto:ztur...@google.com>> wrote:
On Tue, Nov 20, 2018 at 8:51 AM Alexand
https://bugs.llvm.org/show_bug.cgi?id=39727
Bug ID: 39727
Summary: Support for breakpad symbols in LLDB
Product: lldb
Version: unspecified
Hardware: PC
OS: All
Status: NEW
Severity: enhancement
P
