Odd... usually running it from ipython introduces more potential problems, not less.
Were they running mayapy, or a 'normal' python executable? - Paul On Sat, May 22, 2010 at 12:49 AM, Shaun Friedberg (Pyrokinesis) <[email protected]> wrote: > 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. > > > -----Original Message----- > From: [email protected] > [mailto:[email protected]] On Behalf Of Paul Molodowitch > Sent: Saturday, May 22, 2010 11:27 AM > To: python_inside_maya > Subject: [Maya-Python] Segmentation faults in linux 2011 mayapy > > 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 > > -- > http://groups.google.com/group/python_inside_maya -- http://groups.google.com/group/python_inside_maya
