[Author Prev][Author Next][Thread Prev][Thread Next][Author Index][Thread Index]

Re: [pygame] Surfarray.array_alpha() bugfix, py2exe/py2app segfault



hi,

have a look at this setup.py file... I got it making an .exe with
py2exe so maybe it can help you.
http://code.google.com/p/eyestabs/source/browse/trunk/setup.py

Especially look at the numpy parts.

cheers,


On Tue, Feb 3, 2009 at 1:38 PM, Zack Schilling <zack.schilling@xxxxxxxxx> wrote:
> NumPy is definitely included. I can see it on the py2app list as it flies
> by, it's in the zip file in the bundle. If I make a test program that uses
> numpy without the surfarray function, it builds and functions properly.
>
> In Mac OS X, GDB reported back the following. In Windows, there were no
> debug symbols, so it just spat a few memory addresses in the where. Same
> initial message though. I couldn't get any useful info out of either.
>
> -Zack
>
> Program received signal EXC_BAD_ACCESS, Could not access memory.
> Reason: KERN_PROTECTION_FAILURE at address: 0x00000000
> 0x00000000 in ?? ()
> (gdb) where
> #0  0x00000000 in ?? ()
> #1  0x01003303 in surf_get_buffer ()
> #2  0x0039470a in PyEval_EvalFrameEx (f=0x16820580, throwflag=0) at
> /home/fb6/loewis/25/Python/ceval.c:3596
> #3  0x00395b86 in PyEval_EvalFrameEx (f=0x16820410, throwflag=0) at
> /home/fb6/loewis/25/Python/ceval.c:3698
> #4  0x00395b86 in PyEval_EvalFrameEx (f=0x168202b0, throwflag=0) at
> /home/fb6/loewis/25/Python/ceval.c:3698
> #5  0x00395b86 in PyEval_EvalFrameEx (f=0x1681f7e0, throwflag=0) at
> /home/fb6/loewis/25/Python/ceval.c:3698
> #6  0x0039671d in PyEval_EvalCodeEx (co=0x8ff98, globals=0x34d20,
> locals=0x0, args=0xa0604, argcount=2, kws=0x0, kwcount=0, defs=0x0,
> defcount=0, closure=0x0) at /home/fb6/loewis/25/Python/ceval.c:2875
> #7  0x0032b103 in function_call (func=0x14f5ab0, arg=0xa05f8, kw=0x0) at
> /home/fb6/loewis/25/Objects/funcobject.c:517
> #8  0x00309dac in PyObject_Call (func=0x14f5ab0, arg=0xa05f8, kw=0x0) at
> /home/fb6/loewis/25/Objects/abstract.c:1861
> #9  0x00311aa7 in instancemethod_call (func=0x15d8f30, arg=0x10410f0,
> kw=0x0) at /home/fb6/loewis/25/Objects/classobject.c:2519
> #10 0x00309dac in PyObject_Call (func=0x15d8f30, arg=0x10410f0, kw=0x0) at
> /home/fb6/loewis/25/Objects/abstract.c:1861
> #11 0x0038ee63 in PyEval_CallObjectWithKeywords (func=0x15d8f30,
> arg=0x10410f0, kw=0x0) at /home/fb6/loewis/25/Python/ceval.c:3481
> #12 0x00313fe2 in PyInstance_New (klass=0x14efde0, arg=0x10410f0, kw=0x0) at
> /home/fb6/loewis/25/Objects/classobject.c:560
> #13 0x00309dac in PyObject_Call (func=0x14efde0, arg=0x10410f0, kw=0x0) at
> /home/fb6/loewis/25/Objects/abstract.c:1861
> #14 0x00391577 in PyEval_EvalFrameEx (f=0x1680d4b0, throwflag=0) at
> /home/fb6/loewis/25/Python/ceval.c:3823
> #15 0x0039671d in PyEval_EvalCodeEx (co=0x8f9f8, globals=0x34d20,
> locals=0x0, args=0x15aaabc, argcount=1, kws=0x0, kwcount=0, defs=0x0,
> defcount=0, closure=0x0) at /home/fb6/loewis/25/Python/ceval.c:2875
> #16 0x0032b103 in function_call (func=0x14f5870, arg=0x15aaab0, kw=0x0) at
> /home/fb6/loewis/25/Objects/funcobject.c:517
> #17 0x00309dac in PyObject_Call (func=0x14f5870, arg=0x15aaab0, kw=0x0) at
> /home/fb6/loewis/25/Objects/abstract.c:1861
> #18 0x00311aa7 in instancemethod_call (func=0x15d89e0, arg=0x18030, kw=0x0)
> at /home/fb6/loewis/25/Objects/classobject.c:2519
> #19 0x00309dac in PyObject_Call (func=0x15d89e0, arg=0x18030, kw=0x0) at
> /home/fb6/loewis/25/Objects/abstract.c:1861
> #20 0x0038ee63 in PyEval_CallObjectWithKeywords (func=0x15d89e0,
> arg=0x18030, kw=0x0) at /home/fb6/loewis/25/Python/ceval.c:3481
> #21 0x00313fe2 in PyInstance_New (klass=0x1042300, arg=0x18030, kw=0x0) at
> /home/fb6/loewis/25/Objects/classobject.c:560
> #22 0x00309dac in PyObject_Call (func=0x1042300, arg=0x18030, kw=0x0) at
> /home/fb6/loewis/25/Objects/abstract.c:1861
> #23 0x00391577 in PyEval_EvalFrameEx (f=0x9a1e10, throwflag=0) at
> /home/fb6/loewis/25/Python/ceval.c:3823
> #24 0x00395b86 in PyEval_EvalFrameEx (f=0x11bf10, throwflag=0) at
> /home/fb6/loewis/25/Python/ceval.c:3698
> #25 0x0039671d in PyEval_EvalCodeEx (co=0xa3608, globals=0x34d20,
> locals=0x34d20, args=0x0, argcount=0, kws=0x0, kwcount=0, defs=0x0,
> defcount=0, closure=0x0) at /home/fb6/loewis/25/Python/ceval.c:2875
> #26 0x003968d1 in PyEval_EvalCode (co=0xa3608, globals=0x34d20,
> locals=0x34d20) at /home/fb6/loewis/25/Python/ceval.c:514
> #27 0x003ba031 in PyRun_FileExFlags (fp=0xa01ea518, filename=0x29b34
> "/Users/zack/pygametest/dist/main.app/Contents/Resources/main.py",
> start=257, globals=0x34d20, locals=0x34d20, closeit=1, flags=0x0) at
> /home/fb6/loewis/25/Python/pythonrun.c:1273
> #28 0x0038acad in builtin_execfile (self=0x0, args=0x9af80) at
> /home/fb6/loewis/25/Python/bltinmodule.c:703
> #29 0x00394acd in PyEval_EvalFrameEx (f=0x119a60, throwflag=0) at
> /home/fb6/loewis/25/Python/ceval.c:3612
> #30 0x0039671d in PyEval_EvalCodeEx (co=0x819b0, globals=0x34d20,
> locals=0x0, args=0x118c1c, argcount=1, kws=0x118c20, kwcount=0, defs=0x0,
> defcount=0, closure=0x0) at /home/fb6/loewis/25/Python/ceval.c:2875
> #31 0x00393d9e in PyEval_EvalFrameEx (f=0x118ae0, throwflag=0) at
> /home/fb6/loewis/25/Python/ceval.c:3708
> #32 0x0039671d in PyEval_EvalCodeEx (co=0x81ec0, globals=0x34d20,
> locals=0x34d20, args=0x0, argcount=0, kws=0x0, kwcount=0, defs=0x0,
> defcount=0, closure=0x0) at /home/fb6/loewis/25/Python/ceval.c:2875
> #33 0x003968d1 in PyEval_EvalCode (co=0x81ec0, globals=0x34d20,
> locals=0x34d20) at /home/fb6/loewis/25/Python/ceval.c:514
> #34 0x003ba031 in PyRun_FileExFlags (fp=0xa01ea4c0, filename=0xbfffeae8
> "/Users/zack/pygametest/dist/main.app/Contents/Resources/__boot__.py",
> start=257, globals=0x34d20, locals=0x34d20, closeit=0, flags=0x0) at
> /home/fb6/loewis/25/Python/pythonrun.c:1273
> #35 0x003ba3cb in PyRun_SimpleFileExFlags (fp=0xa01ea4c0,
> filename=0xbfffeae8
> "/Users/zack/pygametest/dist/main.app/Contents/Resources/__boot__.py",
> closeit=0, flags=0x0) at /home/fb6/loewis/25/Python/pythonrun.c:879
> #36 0x003ba56e in PyRun_SimpleFile (f=0xa01ea4c0, p=0xbfffeae8
> "/Users/zack/pygametest/dist/main.app/Contents/Resources/__boot__.py") at
> /home/fb6/loewis/25/Python/pythonrun.c:1810
> #37 0x00007b9f in start ()
>
>
>
>
>
> On Feb 2, 2009, at 7:37 PM, René Dudfield wrote:
>
>> Hi,
>>
>> make sure that the numpy files are being included in your py2exe version.
>>
>> Otherwise... try running the bundled version under gdb to see where it is
>> dying.
>>
>>
>> cu,
>>
>>
>>
>> On Tue, Feb 3, 2009 at 10:02 AM, Zack Schilling
>> <zack.schilling@xxxxxxxxx> wrote:
>>>
>>> Well, thanks for reading all that. I'm glad someone is at least looking
>>> at
>>> this stuff.
>>>
>>> I managed to get Numeric installed on my system and while it's old and
>>> crappy, it doesn't segfault the way NumPy does. I'd have a do
>>> considerable
>>> work to move my project over to Numeric, so I won't, especially since it
>>> is
>>> marked for death.
>>>
>>> Do you have any clue why something would run perfectly, not so much as a
>>> warning in the shell, then die if bundled up? It strikes me as odd since
>>> the
>>> parts bundle fine individually yet the code segfaults on both Mac OS X
>>> and
>>> Windows XP when bundled together. I hate it when these problems present
>>> in
>>> ways that appear to be out of my control!
>>>
>>> -Zack
>>>
>>>
>>> On Feb 2, 2009, at 5:24 PM, Marcus von Appen wrote:
>>>
>>>> On, Mon Feb 02, 2009, Zack Schilling wrote:
>>>>
>>>> [numpy surfarray problems]
>>>>
>>>> The more I read about the numpy problems for numpysurfarray and
>>>> numpysndarray, the more I'd love to throw that whole bunch away...
>>>>
>>>> Sorry for being not constructive ;-). If noone else is quicker with
>>>> that, I'll start to rework the whole numpy stuff from next week on or so
>>>> within the pgreloaded branch and port it to the trunk later on - it
>>>> needs some refactoring anyways to get rid of the being-50-times-slower
>>>> issue(s).
>>>>
>>>> Regards
>>>> Marcus
>>>
>>>
>
>