On Fri, Mar 27, 2020, at 11:49, Sumana Harihareswara wrote:
> Benjamin: now that PyCon 2020 has been cancelled, are you considering
> releasing 2.7.18 slightly earlier?
The plan is to follow the dates in PEP 373.
___
Python-Dev mailing list --
[Skip Montanaro ]
> ...
> I thought setting PYTHONTRACEMALLOC should provoke some useful output,
> but I was confused into thinking I was (am?) still missed something
> because it continued to produce this message:
>
> Enable tracemalloc to get the memory block allocation traceback
Ah, I
Hello.
I need to set a PyEval_SetTrace with a new class instance.
All examples use simple function.
PyEval_SetTrace(trace_trampoline, obj);
Following my problem:
I start three threads, but I need to check trace C just one thread.
If I run a while on C trace on thread, it stops all threads.
So,
Victor> I wrote the feature (both tracemalloc and query tracemalloc when a
Victor> buffer overflow is detected), so I should be able to help you ;-)
Yes, I thought you might. :-)
I've attached the output of a more complete run. The command is
% PYTHONTRACEMALLOC=5 ./python
[Skip Montanaro ]
> I've got a memory issue in my modified Python interpreter I'm trying
> to debug. Output at the end of the problematic unit test looks like this:
To my eyes, you left out the most important part ;-) A traceback
showing who made the fatal free() call to begin with.
In debug
Hi Skip,
I wrote the feature (both tracemalloc and query tracemalloc when a
buffer overflow is detected), so I should be able to help you ;-)
Le dim. 5 avr. 2020 à 00:27, Skip Montanaro a écrit :
> Looking at the tracemalloc module docs and trying various command line args
> (-X
I've got a memory issue in my modified Python interpreter I'm trying to
debug. Output at the end of the problematic unit test looks like this:
...
== Tests result: FAILURE then SUCCESS ==
1 test OK.
1 re-run test:
test_rattlesnake
Total duration: 2.9 sec
Tests result: FAILURE then SUCCESS
