On 5/10/2012 4:27 PM, Ari Shapiro wrote:
> Can you run this in gdb and send me the backtrace?

Indeed I can...

#0  0x0000000000000000 in ?? ()
#1  0x00000001052bff67 in PyEval_GetGlobals ()
#2  0x00000001052e0282 in PyImport_Import ()
#3  0x00000001052e04b8 in PyImport_ImportModule ()
#4  0x000000010283b0e9 in boost::python::import (name=<value temporarily 
unavailable, due to optimizations>) at libs/python/src/import.cpp:22
#5  0x00000001004a0372 in initPython () at IceRandom.h:29
#6  0x000000010003bfe8 in main () at IceRandom.h:29

I don't know where it got that IceRandom.h, seeing that initPython 
really seems to be in SBPython.cpp.

By the way, I inserted an fprintf in import.cpp to verify that the value 
being passed by boost::python::import to PyImport_ImportModule is 
"__main__".


>
> -----Original Message-----
> From: James Walker [mailto:[email protected]]
> Sent: Thursday, May 10, 2012 3:45 PM
> To: Ari Shapiro
> Cc: [email protected]
> Subject: Re: [SmartBody-dev] compile errors
>
> On 5/10/2012 3:10 PM, Ari Shapiro wrote:
>> You should use Python 2.6, since that matches BOOST 1.44
>
> Hmm.  The crash report's list of binary image has the lines
>
> org.python.python 2.6.1 (2.6.1)<126DA8FF-5BC2-8788-51E3-D7A29A3F9F0F>
> /System/Library/Frameworks/Python.framework/Versions/2.6/Python
>
> and also
>
> +org.python.python 2.7.2, (c) 2004-2011 Python Software Foundation.
> (2.7.2)<49D18B1A-C92D-E32E-A7C1-086D0B14BD76>
> /Library/Frameworks/Python.framework/Versions/2.7/Python
>
> I don't really know what that means.
>
> I tried using the environment variable
>
> VERSIONER_PYTHON_VERSION=2.6
>
> but it didn't make any difference.
>
>
>>
>> -----Original Message-----
>> From: James Walker [mailto:[email protected]]
>> Sent: Thursday, May 10, 2012 2:58 PM
>> To: Ari Shapiro
>> Cc: [email protected]
>> Subject: Re: [SmartBody-dev] compile errors
>>
>> On 5/10/2012 1:40 PM, Ari Shapiro wrote:
>>> Can you use:
>>>
>>> DYLD_LIBRARY_PATH
>>>
>>> to set the location of the older BOOST version?
>>
>> That was a good idea, but it didn't fix the crash.  The crash report does 
>> indicate that it's now using boost dylibs from my boost_1_44_0/stage/lib 
>> folder, but otherwise the crash looks the same.
>>
>> Is there a particular version of python I need to be using?
>>
>>>
>>> Ari
>>>
>>>
>>> -----Original Message-----
>>> From: James Walker [mailto:[email protected]]
>>> Sent: Thursday, May 10, 2012 12:17 PM
>>> To: Ari Shapiro
>>> Cc: [email protected]
>>> Subject: Re: [SmartBody-dev] compile errors
>>>
>>> On 5/10/2012 11:28 AM, Ari Shapiro wrote:
>>>> Hi James,
>>>>
>>>> I updated the code this morning with those fixes, so those errors 
>>>> shouldn't be there anymore.
>>>
>>> Oh, OK, I'll try to remember to run svn update more frequently.  Thanks.
>>>
>>>> Were you able to successfully build and run SmartBody?
>>>
>>> Build, yes.  Run, no.  When I try to run sbm-fltk, I get this output:
>>>
>>> SocketOpenTcp() failed
>>> Segmentation fault
>>>
>>> and here's the most likely relevant part of the crash report:
>>>
>>> Thread 0 Crashed:  Dispatch queue: com.apple.main-thread
>>> 0   ???                             000000000000000000 0 + 0
>>> 1   org.python.python               0x00000001052ce282 PyImport_Import + 50
>>> 2   org.python.python               0x00000001052ce4b8
>>> PyImport_ImportModule + 40
>>> 3   libboost_python.dylib           0x00000001028290e9
>>> boost::python::import(boost::python::str) + 73 (import.cpp:20)
>>> 4   sbm-fltk                        0x000000010049d845
>>> initPython(std::string) + 74
>>> 5   sbm-fltk                        0x000000010003b8b8 main + 5664
>>> 6   sbm-fltk                        0x00000001000397e8 start + 52
>>>
>>>
>>> I'm guessing it might be because /usr/local/lib contains the too-new 
>>> version of boost.
>>
>>
>
>


-- 
   James W. Walker, Innoventive Software LLC
   <http://www.frameforge3d.com/>

------------------------------------------------------------------------------
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and 
threat landscape has changed and how IT managers can respond. Discussions 
will include endpoint security, mobile security and the latest in malware 
threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
_______________________________________________
Smartbody-developer mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/smartbody-developer

Reply via email to