[Maya-Python] Segmentation faults in linux 2011 mayapy

236 views
Skip to first unread message

Paul Molodowitch

unread,
May 21, 2010, 7:27:02 PM5/21/10
to python_inside_maya
Hi all - in linux, whenever we raise an uncaught exception in maya
2011's mayapy after maya.standalone.initialize(), it seems to cause a
segmentation fault and a hard crash - ie, running:

mayapy -c "import maya.standalone; maya.standalone.initialize(); raise
Exception"

causes:

Traceback (most recent call last):
File "<string>", line 1, in <module>
Exception

maya encountered a fatal error

Signal: 11 (Unknown Signal)
Segmentation fault
Exit 139


I was wondering if anybody else was seeing this as well - we're using
Fedora 10 here, which isn't an officially blessed OS, so I was curious
if it was something peculiar to our OS / configuration.

Thanks,

Paul

--
http://groups.google.com/group/python_inside_maya

Shaun Friedberg (Pyrokinesis)

unread,
May 22, 2010, 3:49:10 AM5/22/10
to python_in...@googlegroups.com
Funny, someone else was having this same problem today, running standalone
from a python shell.
I noticed that running it from an ipython shell worked. Haven't taken the
time to debug it any further.
--
http://groups.google.com/group/python_inside_maya

Paul Molodowitch

unread,
May 22, 2010, 9:37:24 PM5/22/10
to python_in...@googlegroups.com
Odd... usually running it from ipython introduces more potential
problems, not less.

Were they running mayapy, or a 'normal' python executable?

- Paul
--
http://groups.google.com/group/python_inside_maya

Shaun Friedberg (Pyrokinesis)

unread,
May 23, 2010, 5:53:45 AM5/23/10
to python_in...@googlegroups.com
I have never had any problems with Ipython, interesting to hear you have :)
In this case he was attempting to run the script in an interactive python
shell.
He has his environment set up correctly so there is no need to use mayapy.(I
never do)

Sounds like this is coming up for other people as well. Good luck figuring
it out, let us know what you come up with.
--
http://groups.google.com/group/python_inside_maya

Michiel Duvekot

unread,
May 23, 2010, 2:46:04 PM5/23/10
to python_in...@googlegroups.com
Not sure if this helps any, but running it from a Maya terminal
(/Applications/Autodesk/maya2011/Maya\ Terminal.term) under OS X
gives:

michiel$ mayapy -c "import maya.standalone;
maya.standalone.initialize(); raise Exception"
Traceback (most recent call last):
File "<string>", line 1, in <module>
Exception

--
Michiel

--
http://groups.google.com/group/python_inside_maya

Paul Molodowitch

unread,
May 23, 2010, 4:27:19 PM5/23/10
to python_in...@googlegroups.com
On Sun, May 23, 2010 at 11:46 AM, Michiel Duvekot <mduv...@gmail.com> wrote:
> Not sure if this helps any, but running it from a Maya terminal
> (/Applications/Autodesk/maya2011/Maya\ Terminal.term) under OS X
> gives:
>
> michiel$ mayapy -c "import maya.standalone;
> maya.standalone.initialize(); raise Exception"
> Traceback (most recent call last):
>  File "<string>", line 1, in <module>
> Exception

Yeah - that's the expected / normal behavior. Thanks for the input, though . =)

As for ipython - I've never really had any major problems -
occasionally just issues with formatting of output, or with
tracebacks, mostly. On the whole, I think it's a wonderful tool... I
feel like I've had a limb but off whenever I have to use a "normal"
interpreter. =) But for debugging low level stuff like this, I like
to get as pure as possible...

- Paul
- Paul
--
http://groups.google.com/group/python_inside_maya
Reply all
Reply to author
Forward
0 new messages