[ python-Bugs-1189248 ] Seg Fault when compiling small program

[SourceForge.net]

Bugs item #1189248, was opened at 2005-04-25 07:00
Message generated for change (Comment added) made by doerwalter
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=105470&aid=1189248&group_id=5470

Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: Python Interpreter Core
Group: Python 2.4
>Status: Closed
>Resolution: Out of Date
Priority: 5
Submitted By: Reginald B. Charney (rcharney)
Assigned to: Nobody/Anonymous (nobody)
Summary: Seg Fault when compiling small program

Initial Comment:
I am using SuSE 9.2. When trying to compile/interpret
the attached file, the python interpreter seg faults
with no other information.

Please note: the attached test file does not end in a
new line.

----------------------------------------------------------------------

>Comment By: Walter Dörwald (doerwalter)
Date: 2005-08-31 19:18

Message:
Logged In: YES 
user_id=89016

Martins patch to pythonrun.c (2.216/2.211.2.2) should have
finally fixed this completely. On Linux I get "SyntaxError:
'unknown encoding: evilascii' (evil.py, line 1)". Closing as
out of date.

----------------------------------------------------------------------

Comment By: Reinhold Birkenfeld (birkenfeld)
Date: 2005-06-04 13:45

Message:
Logged In: YES 
user_id=1188172

I believe it is fixed, too... can't reproduce here.

----------------------------------------------------------------------

Comment By: Michael Hudson (mwh)
Date: 2005-04-25 09:56

Message:
Logged In: YES 
user_id=6656

I think this is fixed in Python 2.4.1... what version are you using?

----------------------------------------------------------------------

Comment By: Reginald B. Charney (rcharney)
Date: 2005-04-25 08:42

Message:
Logged In: YES 
user_id=411372

It turns out that the seg fault was caused by the first line
of the program:

# coding: evil

It seems that specifying an invalid character encoding
causes a seg fault.

----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=105470&aid=1189248&group_id=5470