➜

This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author Howard_Landman
Recipients Howard_Landman
Date 2020-08-03.21:14:23
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1596489263.54.0.830343575979.issue41335@roundup.psfhosted.org>
In-reply-to
Content 
It appears to be in the spidev library xfer method, when used for reading. Calling that 107.4M times (using the same code as inside my read_regs24() method) causes the free() error.

Breakpoint 1, malloc_printerr (str=0x76e028f8 "free(): invalid pointer")
    at malloc.c:5341
5341	malloc.c: No such file or directory.
(gdb) bt
#0  malloc_printerr (str=0x76e028f8 "free(): invalid pointer") at malloc.c:5341
#1  0x76d44d50 in _int_free (av=0x76e1f7d4 <main_arena>, 
    p=0x43417c <small_ints.lto_priv+72>, have_lock=<optimized out>) at malloc.c:4165
#2  0x001b4f40 in list_dealloc (op=0x766d0f58) at ../Objects/listobject.c:324
#3  0x7669b660 in ?? ()
   from /usr/lib/python3/dist-packages/spidev.cpython-37m-arm-linux-gnueabihf.so
Backtrace stopped: previous frame identical to this frame (corrupt stack?)

Should I be worried about the "corrupt stack" message?
History
Date User Action Args
2020-08-03 21:14:23Howard_Landmansetrecipients: + Howard_Landman
2020-08-03 21:14:23Howard_Landmansetmessageid: <1596489263.54.0.830343575979.issue41335@roundup.psfhosted.org>
2020-08-03 21:14:23Howard_Landmanlinkissue41335 messages
2020-08-03 21:14:23Howard_Landmancreate