[Author Prev][Author Next][Thread Prev][Thread Next][Author Index][Thread Index]
[pygame] BUG: pygame 1.8 crash on osx in run_tests.py
Hello All,
I have the lastest pygame 1.8pre svn 
dhc15:~/svn/pygame/trunk noinfo$ svn update
At revision 965.
On a macbook pro running 10.4.8
dhc15:~ noinfo$ uname -a
Darwin dhc15 8.8.1 Darwin Kernel Version 8.8.1: Mon
Sep 25 19:42:00 PDT 2006; root:xnu-792.13.8.obj~1/RELEASE_I386 i386 i386
I get a crash during python run_tests.py after an install (python
setup.py install)
I am getting a crash in the sdl_mixer during the display test. I don't
know if it has to do with the double free errors I am getting or a bug
in the sdl_mixer code itself.
My stack trace is 
Date/Time:      2006-11-06 22:50:18.343 -0800
OS Version:     10.4.8 (Build 8L2127)
Report Version: 4
Command: Python
Path:
/Library/Frameworks/Python.framework/Versions/2.4/Resources/Python.app/Contents/MacOS/Python
Parent:  bash [1779]
Version: 2.4a0 (2.4alpha1)
PID:    16530
Thread: 0
Exception:  EXC_BAD_ACCESS (0x0001)
Codes:      KERN_INVALID_ADDRESS (0x0001) at 0x55555555
Thread 0 Crashed:
0   SDL_mixer                 	0x3201a6c2 open_file + 376
1   SDL_mixer                 	0x32024ae3 read_config_file + 100
2   SDL_mixer                 	0x320256ad Timidity_Init + 27
3   SDL_mixer                 	0x320193b3 open_music + 415
4   SDL_mixer                 	0x32017750 Mix_OpenAudio + 149
5   mixer.so                  	0x01793741 autoinit + 285 (mixer.c:189)
6   org.python.python         	0x0020e293 PyObject_Call + 45
(abstract.c:1795)
7   org.python.python         	0x002799b6 PyEval_CallObjectWithKeywords
+ 112 (ceval.c:3430)
8   org.python.python         	0x0020e264 PyObject_CallObject + 32
(abstract.c:1787)
9   base.so                   	0x005ed366 init + 552 (base.c:159)
10  org.python.python         	0x0027fe66 PyEval_EvalFrame + 22313
(ceval.c:3563)
11  org.python.python         	0x00280179 PyEval_EvalFrame + 23100
(ceval.c:3645)
12  org.python.python         	0x00280b92 PyEval_EvalCodeEx + 1774
(ceval.c:2736)
the bug is almost identical to this one
http://www.libsdl.org/pipermail/sdl/2006-June/074829.html