Python 2.2.1 bug

Roman Suzi rnd at
Mon Aug 26 07:06:35 CEST 2002

On Mon, 26 Aug 2002, Allen Edwards wrote:

>I am also unable to create this "bug".  I'm running Win XP Pro, with 1GB 
>  RAM.
>PythonWin 2.2.1 (#34, Apr 15 2002, 09:51:39) [MSC 32 bit (Intel)] on win32.
>Portions Copyright 1994-2001 Mark Hammond (mhammond at - 
>see 'Help/About PythonWin' for further copyright information.
> >>> eval("int" + ".__call__"*100000)
><method-wrapper object at 0x0116BDE0>
> >>>
>Pavel Pergamenshchik wrote:
>> I found a way to break Python 2.2.1 (at least) both on Linux and Windows.
>> Type
>> eval("int" + ".__call__"*100000)\n
>> at the prompt, then press ctrl-D or ctrl-Z to edit. This will result in a
>> segfault on Linux and some weird "unknown software exception" thing on
>> Windows.

It showed Seg fault only once. And it happened when I 
pressed Ctrl-C. Then the same actions didnt produce
segfaults. So, probably, it is a bug with timing conditions.

Sincerely yours, Roman Suzi
rnd at =\= My AI powered by Linux RedHat 7.2
aaro at <- not to be mailed to

More information about the Python-list mailing list