Message 409895 - Python tracker

➜

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	pablogsal
Recipients	eric.smith, nanjekyejoannah, pablogsal, zach.ware
Date	2022-01-06.18:41:10
SpamBayes Score	-1.0
Marked as misclassified	Yes
Message-id	<1641494470.73.0.4340262467.issue46280@roundup.psfhosted.org>
In-reply-to

Content
> I don't see how this could be an uninitialized read, although I'm willing to be wrong. It can be uninitialized if the parenstack[nested_depth] value is itself initialized, which can happen if the memory block pointed by parenstack has not been initialized to some value after malloc'ed and parenstack[nested_depth] never got a value. But yeah, a lot of hypotheticals here that I am sure are not possible in the actual code.

> I don't see how this could be an uninitialized read, although I'm willing to be wrong.

It can be uninitialized if the parenstack[nested_depth] value is itself initialized, which can happen if the memory block pointed by parenstack has not been initialized to some value after malloc'ed and parenstack[nested_depth] never got a value.

But yeah, a lot of hypotheticals here that I am sure are not possible in the actual code.

History
Date	User	Action	Args
2022-01-06 18:41:10	pablogsal	set	recipients: + pablogsal, eric.smith, zach.ware, nanjekyejoannah
2022-01-06 18:41:10	pablogsal	set	messageid: <1641494470.73.0.4340262467.issue46280@roundup.psfhosted.org>
2022-01-06 18:41:10	pablogsal	link	issue46280 messages
2022-01-06 18:41:10	pablogsal	create