[issue8352] imp.find_module of a .py ending dir causes glibc double free crash

Florent Xicluna added the comment: It looks like a duplicate of #7732. -- nosy: +flox resolution: -> duplicate status: open -> closed superseder: -> imp.find_module crashes Python if there exists a directory named "__init__.py" ___ Python tracker

[issue8352] imp.find_module of a .py ending dir causes glibc double free crash

Senthil Kumaran added the comment: No, that is not bpython interpreter. The a crash report on "python interpreter" observed with imp module when a directory ends with .py. -- nosy: +orsenthil ___ Python tracker __

[issue8352] imp.find_module of a .py ending dir causes glibc double free crash

Shashwat Anand added the comment: mkdir bla.py; python -c 'import imp; imp.find_module("bla", ["."])' This causes bpython to crash after the first input char if such a directory exist. I am sure you do not mean 'bpython intepretor' here. -- nosy: +l0nwlf _

[issue8352] imp.find_module of a .py ending dir causes glibc double free crash

Changes by Ezio Melotti : -- nosy: +brett.cannon, ncoghlan priority: -> high stage: -> test needed type: -> crash versions: -Python 2.5 ___ Python tracker ___

[issue8352] imp.find_module of a .py ending dir causes glibc double free crash

New submission from Matthias Klose : [forwarded from http://bugs.debian.org/577005] seen with 2.5.5, 2.6.5 and 2.7alpha4: The imp.find_module function causes a glibc double free or corruption if it would be invoked with a directory with a ".py" ending. It can be reproduced with: mkdir bla.py;