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 Alexander Riccio
Recipients Alexander Riccio, Jim.Jewett, loewis, paul.moore, serhiy.storchaka, skrah, steve.dower, tim.golden, zach.ware
Date 2019-04-19.02:04:58
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1555639498.58.0.908054626636.issue25878@roundup.psfhosted.org>
In-reply-to
Content
One more thing, after I ran code analysis:

This is obviously a potential memory leak:
Warning	C6308	'realloc' might return null pointer: assigning null pointer to 'arr->items', which is passed as an argument to 'realloc', will cause the original memory block to be leaked.
cpython\parser\parsetok.c	38	


I found some sketchy code that isn't obviously correct. Here are a few of the warnings:


Warning	C6294	Ill-defined for-loop:  initial condition does not satisfy test.  Loop body not executed.
\cpython\modules\gcmodule.c	1377	


Warning	C6011	Dereferencing NULL pointer 'cmdline'. See line 230 for an earlier location where this can occur
\cpython\python\preconfig.c	242	
(cmdline is checked for nullness after several uses?)


And finally there's one warning where I have no clue what's going on:

Warning	C6386	Buffer overrun while writing to 'x_digits':  the writable size is '10' bytes, but '286331156' bytes might be written.	
\cpython\objects\longobject.c	2972
History
Date User Action Args
2019-04-19 02:04:58Alexander Ricciosetrecipients: + Alexander Riccio, loewis, paul.moore, tim.golden, skrah, Jim.Jewett, zach.ware, serhiy.storchaka, steve.dower
2019-04-19 02:04:58Alexander Ricciosetmessageid: <1555639498.58.0.908054626636.issue25878@roundup.psfhosted.org>
2019-04-19 02:04:58Alexander Ricciolinkissue25878 messages
2019-04-19 02:04:58Alexander Ricciocreate