[issue34113] LLTRACE segv

STINNER Victor added the comment: Thanks Constantin Petrisor to fix and thanks Andrew Valencia for the bug report! It was the first time that I see a bug report on LLTRACE on the last 5 years, it seems like almost no one uses it. Likely because you need to compile Python manually (or find a

[issue34113] LLTRACE segv

STINNER Victor added the comment: New changeset 8ed317f1ca42a43df14282bbc3ccc0b5610432f4 by Victor Stinner (costypetrisor) in branch 'master': bpo-34113: Fix a crash when using LLTRACE is on (GH-8517) https://github.com/python/cpython/commit/8ed317f1ca42a43df14282bbc3ccc0b5610432f4

[issue34113] LLTRACE segv

STINNER Victor added the comment: By the way, see also bpo-25571. -- nosy: +vstinner ___ Python tracker ___ ___ Python-bugs-list ma

[issue34113] LLTRACE segv

Petr Viktorin added the comment: The problem here is that tracing for STACKADJ prints out the top of the stack *after* adjustment. This is OK for growing the stack, but not for shrinking it (e.g. calling STACKADJ(-3) pops off three things at once, which can leave TOP undefined when it's prin

[issue34113] LLTRACE segv

Change by Petr Viktorin : -- nosy: +petr.viktorin ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: https://mai

[issue34113] LLTRACE segv

Change by Roundup Robot : -- keywords: +patch pull_requests: +8033 stage: -> patch review ___ Python tracker ___ ___ Python-bugs-li

[issue34113] LLTRACE segv

New submission from Andrew Valencia : Build with -DLLTRACE, then: >>> __lltrace__ = 1 >>> a = [1, 2, 3] 0: 100, 0 push 1 3: 100, 1 push 2 6: 100, 2 push 3 9: 103, 3 pop 3 pop 2 pop 1 push [1, 2, 3] 12: 90, 0 pop [1, 2, 3] 15: 100, 3 push None 18: 83 pop None >>> a[0] = 1 0: 100, 0 push 1 3: 10