Message374117
I don't think changing the documentation makes this not be a bug. My situation: I have a Python 3.7.3 program that reliably dies (after about 13 hours, having called its measure() method between 118.6M and 118.7M times) with free(): invalid pointer, which calls abort(). I believe that this is a bug in Python; and it's NOT a memory leak, since the size of the program doesn't change at all over time and is under 14 MB (real). I would like to debug it. This basically says "you're screwed". I can't catch the abort, and I can't use python3-dbg because it won't bind with the RPi.GPIO or spidev libraries. So all I can get from a core dump is that free() is being called by list_ass_item() at ../Objects/listobject.c line 739. Assuming that I'm right and that this is a bug in Python, how do you expect anyone to ever debug it? At a bare minimum, there needs to be an easy way to get a full stack trace through both Python and C. |
|
Date |
User |
Action |
Args |
2020-07-23 00:56:59 | Howard_Landman | set | recipients:
+ Howard_Landman, vstinner, kisielk, python-dev, dtcaciuc |
2020-07-23 00:56:59 | Howard_Landman | set | messageid: <1595465819.28.0.300625846234.issue12423@roundup.psfhosted.org> |
2020-07-23 00:56:59 | Howard_Landman | link | issue12423 messages |
2020-07-23 00:56:58 | Howard_Landman | create | |
|