[ python-Bugs-1777057 ] memoryview('test') is causing a segfault

SourceForge.net noreply at sourceforge.net
Sun Aug 19 06:25:00 CEST 2007


Bugs item #1777057, was opened at 2007-08-18 18:13
Message generated for change (Comment added) made by nnorwitz
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=105470&aid=1777057&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 3000
>Status: Closed
>Resolution: Fixed
Priority: 8
Private: No
Submitted By: Christian Heimes (tiran)
>Assigned to: Neal Norwitz (nnorwitz)
Summary: memoryview('test') is causing a segfault

Initial Comment:
./python -c "memoryview('test')"
Segmentation fault

I compiled Python 3.0 with 
$ ./configure --with-pydebug --enable-unicode=ucs4
and 
$ make EXTRA_CFLAGS="-DPy_REF_DEBUG -DPy_TRACE_REFS -DPy_DEBUG"
after a make clean; rm -rf build; svn up

I've used gdb to trace the segfault:

Program received signal SIGSEGV, Segmentation fault.
[Switching to Thread -1210415424 (LWP 14436)]
0x080f77a0 in PyErr_SetObject (exception=0x81962c0, value=0xb7cee3a8) at Python/errors.c:55
55              if (exception != NULL &&



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

>Comment By: Neal Norwitz (nnorwitz)
Date: 2007-08-18 21:25

Message:
Logged In: YES 
user_id=33168
Originator: NO

Committed revision 57193.  This problem was due to not initializing the
new BufferError properly.  Travis mentioned this in his post to
python-3000.

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

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


More information about the Python-bugs-list mailing list