Bugs item #983311, was opened at 2004-07-01 11:42
Message generated for change (Settings changed) made by birkenfeld
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=105470&aid=983311&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.3
>Status: Closed
>Resolution: Out of Date
Priority: 5
Submitted By: Simon Michael (simon)
Assigned to: Nobody/Anonymous (nobody)
Summary: simple attribute access causing segfault in certain cases
Initial Comment:
Reproduce:
zopectl debug (done in zope debugger to get necessary
imports)
>>> from AccessControl.tests.testSecurity import
SecurityTests
>>> SecurityTests.doc_class
Python 2.3.4 crashes silently. Python 2.3.3 works
normally on the same machine. This is some virtual
server variant of debian gnu/linux on intel
(aktiom.net. On another machine (standard debian i386)
Python 2.3.3 shows the same crash.
That attr in
zope/lib/python/AccessControl/tests/testSecurity.py
looks like:
class SecurityTests (DTMLTests):
doc_class = UnownedDTML # another class
Cf http://zwiki.org/IssueNo0860 .
----------------------------------------------------------------------
>Comment By: Georg Brandl (birkenfeld)
Date: 2006-01-10 23:00
Message:
Logged In: YES
user_id=1188172
I think yes.
----------------------------------------------------------------------
Comment By: Michael Hudson (mwh)
Date: 2004-07-14 10:56
Message:
Logged In: YES
user_id=6656
Uh, there seems little chance this is a Python core bug. Can we
close this report?
----------------------------------------------------------------------
Comment By: Andy Dustman (adustman)
Date: 2004-07-13 22:02
Message:
Logged In: YES
user_id=71372
This may or may not be related: I've had scattered reports
of people having trouble with attribute access (maybe) with
MySQLdb-1.0.0 on Python-2.3.4 (and maybe 2.3.3 but not 2.2)
on *BSD and Mac OS X, but I can't reproduce it on Linux
(x86) with 2.3.4. One person is getting a segfault upon
import (this is not in the bug listed below); I am trying to
get a gdb backtraces.
https://sourceforge.net/tracker/index.php?func=detail&aid=970667&group_id=22307&atid=374932
----------------------------------------------------------------------
Comment By: Simon Michael (simon)
Date: 2004-07-13 21:33
Message:
Logged In: YES
user_id=572
See also discussion at http://collector.zope.org/Zope/1395
----------------------------------------------------------------------
Comment By: Armin Rigo (arigo)
Date: 2004-07-01 22:21
Message:
Logged In: YES
user_id=4771
What I mean here is that you should report this bug to Zope, not to Python,
unless there is a good reason to suspect that a bug in the Python core is
causing it. But to me it really looks like a bug in the Zope extension module,
which for some reason shows up only with some version of Python or on some
platform.
----------------------------------------------------------------------
Comment By: Simon Michael (simon)
Date: 2004-07-01 21:25
Message:
Logged In: YES
user_id=572
UnownedDTML is indeed a zope extension class.
----------------------------------------------------------------------
Comment By: Armin Rigo (arigo)
Date: 2004-07-01 17:20
Message:
Logged In: YES
user_id=4771
If this bug involves C extension modules specific to Zope
then I'd first consider it as a bug in one of these modules.
I would be particularly suspicious that this is the case in
a file called testSecurity: isn't its goal to check some
C-implemented security feature of Zope?
If I am wrong please try to provide a Python code sample.
Reading a class attribute out of some class tends to work
just fine.
----------------------------------------------------------------------
Comment By: Andreas Jung (ajung)
Date: 2004-07-01 12:34
Message:
Logged In: YES
user_id=11084
Works for me with Python 2.3.3/4 on three different Linux
systems.
----------------------------------------------------------------------
Comment By: Simon Michael (simon)
Date: 2004-07-01 11:52
Message:
Logged In: YES
user_id=572
> Python 2.3.3 works normally on the same machine.
I meant: Python 2.3.3 works normally on another, similar
machine (virtual linux host).
----------------------------------------------------------------------
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=105470&aid=983311&group_id=5470
_______________________________________________
Python-bugs-list mailing list
Unsubscribe:
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
