segfault when running smtplib example

[bertramscharpf]

BPO	1003195
Nosy	@terryjreedy, @facundobatista, @jcea, @ronaldoussoren

^{Note: these values reflect the state of the issue at the time it was migrated and might not reflect the current state.}

Show more details

GitHub fields:

assignee = None
closed_at = <Date 2013-03-20.21:20:34.555>
created_at = <Date 2004-08-04.11:43:34.000>
labels = ['interpreter-core', 'type-crash']
title = 'segfault when running smtplib example'
updated_at = <Date 2013-03-20.21:20:34.553>
user = 'https://bugs.python.org/bertramscharpf'

bugs.python.org fields:

activity = <Date 2013-03-20.21:20:34.553>
actor = 'terry.reedy'
assignee = 'none'
closed = True
closed_date = <Date 2013-03-20.21:20:34.555>
closer = 'terry.reedy'
components = ['Interpreter Core']
creation = <Date 2004-08-04.11:43:34.000>
creator = 'bertramscharpf'
dependencies = []
files = []
hgrepos = []
issue_num = 1003195
keywords = []
message_count = 8.0
messages = ['21932', '21933', '21934', '21935', '21936', '152018', '152114', '184797']
nosy_count = 7.0
nosy_names = ['terry.reedy', 'facundobatista', 'jcea', 'ronaldoussoren', 'bertramscharpf', 'neologix', 'Jon.Bringhurst']
pr_nums = []
priority = 'normal'
resolution = 'wont fix'
stage = 'test needed'
status = 'closed'
superseder = None
type = 'crash'
url = 'https://bugs.python.org/issue1003195'
versions = ['Python 2.6']

[bertramscharpf]

On my system, running the simple smtplib Example
from the Documentation results in a segmentation fault.
Execution stops and no mail is submitted.

I debugged into the Python source code, but my
understanding of the inner mechanisms doesn't
suffice to fix the problem.

I update my system periodically using "apt-get update ;
apt-get upgrade". I don't remember, when it was the last
time Python was upgraded.

I made the files availabe:

http://www.bertram-scharpf.de/tmp/smtpex.py.txt
http://www.bertram-scharpf.de/tmp/smtpex.desc.txt

[ronaldoussoren]

Logged In: YES
user_id=580910

I cannot reproduce this.

I've tested:

Python 2.3 (#1, Sep 13 2003, 00:49:11)
[GCC 3.3 20030304 (Apple Computer, Inc. build 1495)] on darwin
Type "help", "copyright", "credits" or "license" for more information.

Python 2.3.4 (#2, Jul 5 2004, 09:15:05)
[GCC 3.3.4 (Debian 1:3.3.4-2)] on linux2

Python 2.2.3+ (#1, Jun 20 2004, 13:32:48)
[GCC 3.3.4 (Debian)] on linux2

The first is the system python on MacOS X, the other two are current
Debian packages (python2.3 and python2.2) on Debian stable.

[bertramscharpf]

Logged In: YES
user_id=1097255

Indeed, I did compile python 2.2.1 with Gcc versions 2.95,
3.0 and 3.3. The segfault only occurs in the 2.95 compiled code.

[facundobatista]

Logged In: YES
user_id=752496

Please, could you verify if this problem persists in Python 2.3.4
or 2.4?

If yes, in which version? Can you provide a test case?

If the problem is solved, from which version?

Note that if you fail to answer in one month, I'll close this bug
as "Won't fix".

Thank you!

. Facundo

[bertramscharpf]

Logged In: YES
user_id=1097255

I'll close this bug as "Won't fix".

I think that's OK.

[JonBringhurst]

I just ran into this while using the smtplib example on:

2.6 (r26:66714, Jan 17 2012, 11:02:11)
GCC 4.1.2 20080704 (Red Hat 4.1.2-44)

Running the program simply gives a "Segmentation Fault (core dumped)"

Running it under gdb...

[Thread debugging using libthread_db enabled]
[New Thread 0x2b0257007b80 (LWP 2567)]

Program received signal SIGSEGV, Segmentation fault.
PyEval_EvalFrameEx (f=0x17701d00, throwflag=<value optimized out>) at Python/ceval.c:4342
4342 if (!PyDict_Check(gobals)) {

[neologix]

Could you please indicate exactly the command you're running, and provide the full backtrace?

[terryjreedy]

The original poster's links are dead. Without a reproducible problem with a current release, there is nothing we can do. Anyone who can provide such and will respond to requests for more information can reopen.

Note:
On Win 7 with 3.2, 3.3, current example exits on line
server = smtplib.SMTP('localhost')
with
socket.error: [Errno 10061] No connection could be made because the target machine actively refused it