python scripts segfaulting

Coding Python Support
1

Is anyone else getting segfaults trying to run some python scripts on recent svn builds, mainly ones that involve a ui ?

Here is a gdb backtrace when I tried to load the yafaray ui. By no means is it the only one that crashes.

(gdb) backtrace
#0  0x00007f9289766be0 in PyEval_EvalFrameEx ()
   from /usr/lib/libpython2.5.so.1.0
#1  0x00007f928976b25d in PyEval_EvalCodeEx ()
   from /usr/lib/libpython2.5.so.1.0
#2  0x00007f928970271e in ?? () from /usr/lib/libpython2.5.so.1.0
#3  0x00007f92896de763 in PyObject_Call () from /usr/lib/libpython2.5.so.1.0
#4  0x00007f92897635c1 in PyEval_CallObjectWithKeywords ()
   from /usr/lib/libpython2.5.so.1.0
#5  0x000000000094d309 in exec_callback ()
#6  0x000000000094da55 in BPY_spacescript_do_pywin_draw ()
#7  0x00000000006a9b24 in scrarea_do_windraw ()
#8  0x0000000000650e2a in screenmain ()
#9  0x00000000005bfcad in main ()

gen 3


Program received signal SIGSEGV, Segmentation fault.
[Switching to Thread 0x7faf5ae39730 (LWP 10115)]
0x00007faf5a4fcbe0 in PyEval_EvalFrameEx () from /usr/lib/libpython2.5.so.1.0
(gdb) backtrace
#0  0x00007faf5a4fcbe0 in PyEval_EvalFrameEx ()
   from /usr/lib/libpython2.5.so.1.0
#1  0x00007faf5a5009e5 in PyEval_EvalFrameEx ()
   from /usr/lib/libpython2.5.so.1.0
#2  0x00007faf5a50125d in PyEval_EvalCodeEx ()
   from /usr/lib/libpython2.5.so.1.0
#3  0x00007faf5a49871e in ?? () from /usr/lib/libpython2.5.so.1.0
#4  0x00007faf5a474763 in PyObject_Call () from /usr/lib/libpython2.5.so.1.0
#5  0x00007faf5a4f95c1 in PyEval_CallObjectWithKeywords ()
   from /usr/lib/libpython2.5.so.1.0
#6  0x000000000094d309 in exec_callback ()
#7  0x000000000094da55 in BPY_spacescript_do_pywin_draw ()
#8  0x00000000006a9b24 in scrarea_do_windraw ()
#9  0x0000000000650e2a in screenmain ()
#10 0x00000000005bfcad in main ()
(gdb)

discombobulator

Program received signal SIGSEGV, Segmentation fault.
[Switching to Thread 0x7f4c7f5c2730 (LWP 10160)]
0x00007f4c7ec85be0 in PyEval_EvalFrameEx () from /usr/lib/libpython2.5.so.1.0
(gdb) backtrace
#0  0x00007f4c7ec85be0 in PyEval_EvalFrameEx ()
   from /usr/lib/libpython2.5.so.1.0
#1  0x00007f4c7ec8a25d in PyEval_EvalCodeEx ()
   from /usr/lib/libpython2.5.so.1.0
#2  0x00007f4c7ec2171e in ?? () from /usr/lib/libpython2.5.so.1.0
#3  0x00007f4c7ebfd763 in PyObject_Call () from /usr/lib/libpython2.5.so.1.0
#4  0x00007f4c7ec825c1 in PyEval_CallObjectWithKeywords ()
   from /usr/lib/libpython2.5.so.1.0
#5  0x000000000094d309 in exec_callback ()
#6  0x000000000094da55 in BPY_spacescript_do_pywin_draw ()
#7  0x00000000006a9b24 in scrarea_do_windraw ()
#8  0x0000000000650e2a in screenmain ()
#9  0x00000000005bfcad in main ()
(gdb)
2

Best I can figure it broke at r19588.
Anyone else having trouble ?

I am building on 64 bit Ubuntu 8.10 with gcc-4.3

3

You should file a bug.

edit: it builds fine with make, the problem seems to be scons

4

Well that seems to have fixed it - working for me now on r19719.

Hurrah for devs… !

EDIT -

Comment By: Campbell Barton (campbellbarton)
Date: 2009-04-14 17:20

Message:
was an implicit declaration in a macro, fixed in svn r19717