[Cmb-users] Error starting CMB v4 from superbuild
Hines, Amanda M ERDC-RDE-ITL-MS
Amanda.M.Hines at erdc.dren.mil
Mon Jun 8 12:07:20 EDT 2015
Hey David,
1. Yep, you are correct. I wasn¹t a member so it was failing to post my
emails.
3. It appears to be a boost problem. It looks like I am getting junk for
my path
frame #9: 0x00000001125f5388
libRemusServer.dylib`remus::server::detail::WorkerFinder::WorkerFinder(this
=0x00007fff5fbfc3b0, parser=0x000000012059c0c8, ext=0x000000012059c0b0) +
648 at WorkerFinder.cxx:35
32 Info()
33 {
34 boost::filesystem::path cwd = boost::filesystem::current_path();
-> 35 this->parseDirectory(cwd);
36 }
37
38
//------------------------------------------------------------------------
----
(lldb) p cwd
(boost::filesystem::path) $1 = (m_pathname = "?Y \x01")
I have several versions of boost on my machine so I wonder if it is trying
to use the wrong one (I have cmv v3 and data browser which both have their
own builds of boost and then I have v3 and v4 installed in the
applications directory using mac installers).
4. I see the same error from both the install and the cmb-build
directories.
Thanks,
Amanda
On 6/5/15, 2:33 PM, "David Thompson" <david.thompson at kitware.com> wrote:
>Hi Amanda,
>
>A few things:
>
>1. I have not seen your e-mail to the cmb-users list. Is it possible that
>you haven't joined the list yet at
>http://public.kitware.com/mailman/listinfo/cmb-users ? I think the list
>is set to only allow messages from list members, so I see Bob's replies
>to you but not your messages.
>
>2. You are correct that DYLD_LIBRARY_PATH causes problems; you should use
>DYLD_FALLBACK_LIBRARY_PATH as Bob mentioned.
>
>3. I have not seen things break at the place your backtrace mentions; Rob
>might see what's going wrong, since it appears to be dying while looking
>for a mesh worker. (Hi, Rob :-).
>
>4. However, I do see that you are running the installed version of
>ModelBuilder (in
>/Users/rditlaem/Work/Applications/cmb_v4/build/install/Applications). Bob
>has had other issues running from the install tree, so it might be
>related to that. Can you try running from your build directory? (There
>should be a ModelBuilder.app in
>/Users/rditlaem/Work/Applications/cmb_v4/build/cmb/src/cmb-build/bin .)
>
> Thanks,
> David
>
>> Nope, I am not setting the DYLD_LIBRARY_PATH because that causes a
>>problem with the ImageIO lib.
>>
>>>> dyld: Symbol not found: __cg_png_create_info_struct
>>>> Referenced from:
>>>>/System/Library/Frameworks/ImageIO.framework/Versions/A/ImageIO
>>>> Expected in:
>>>>/Users/rditlaem/Work/Applications/cmb_v4/build/install/lib//libPng.dyli
>>>>b
>>>> in /System/Library/Frameworks/ImageIO.framework/Versions/A/ImageIO
>>>> Trace/BPT trap
>> David Thompson said to set the DYLD_FALLBACK_LIBRARY_PATH instead.
>>Here¹s the error in lldb:
>>
>> Process 59213 launched:
>>'/Users/rditlaem/Work/Applications/cmb_v4/build/install/Applications/Mode
>>lBuilder.app/Contents/MacOS/ModelBuilder' (x86_64)
>>
>> Find Session cmb_forwarding
>> Find Session discrete
>> Find Session exodus
>> Find Session native
>> Find Session remus_remote
>> Process 59213 stopped
>> * thread #1: tid = 0x97ab9, 0x000000011247e5f9
>>libstdc++.6.dylib`std::string::_Rep::_M_dispose(std::allocator<char>
>>const&) (.part.23) + 3, queue = 'com.apple.main-thread', stop reason =
>>EXC_BAD_ACCESS (code=1, address=0xfffffffffffffff8)
>> frame #0: 0x000000011247e5f9
>>libstdc++.6.dylib`std::string::_Rep::_M_dispose(std::allocator<char>
>>const&) (.part.23) + 3
>> libstdc++.6.dylib`std::string::_Rep::_M_dispose(std::allocator<char>
>>const&) (.part.23) + 3:
>> -> 0x11247e5f9: lock
>> 0x11247e5fa: xaddl %eax, 0x10(%rdi)
>> 0x11247e5fe: testl %eax, %eax
>> 0x11247e600: jg 0x11247e607 ;
>>std::string::_Rep::_M_dispose(std::allocator<char> const&) (.part.23) +
>>17
>>
>> And the backtrace from lldb:
>>
>> * thread #1: tid = 0x97ab9, 0x000000011247e5f9
>>libstdc++.6.dylib`std::string::_Rep::_M_dispose(std::allocator<char>
>>const&) (.part.23) + 3, queue = 'com.apple.main-thread', stop reason =
>>EXC_BAD_ACCESS (code=1, address=0xfffffffffffffff8)
>> * frame #0: 0x000000011247e5f9
>>libstdc++.6.dylib`std::string::_Rep::_M_dispose(std::allocator<char>
>>const&) (.part.23) + 3
>> frame #1: 0x000000011247a682
>>libstdc++.6.dylib`std::string::assign(std::string const&) + 130
>> frame #2: 0x00000001123e4cfe
>>libboost_filesystem.dylib`boost::filesystem::detail::directory_iterator_c
>>onstruct(boost::filesystem::directory_iterator&, boost::filesystem::path
>>const&, boost::system::error_code*) [inlined]
>>std::string::operator=(__str=0x00007fff5fbfbcb0,
>>this=0x00000001211d3d40) + 350 at basic_string.h:547
>> frame #3: 0x00000001123e4cf3
>>libboost_filesystem.dylib`boost::filesystem::detail::directory_iterator_c
>>onstruct(boost::filesystem::directory_iterator&, boost::filesystem::path
>>const&, boost::system::error_code*) [inlined]
>>boost::filesystem::path::operator=(p=0x00007fff5fbfbcb0,
>>this=0x00000001211d3d40)
>> frame #4: 0x00000001123e4cf3
>>libboost_filesystem.dylib`boost::filesystem::detail::directory_iterator_c
>>onstruct(boost::filesystem::directory_iterator&, boost::filesystem::path
>>const&, boost::system::error_code*) [inlined]
>>boost::filesystem::directory_entry::assign(symlink_st=<unavailable>,
>>st=<unavailable>, p=0x00007fff5fbfbcb0, this=0x00000001211d3d40)
>> frame #5: 0x00000001123e4cf3
>>libboost_filesystem.dylib`boost::filesystem::detail::directory_iterator_c
>>onstruct(it=0x00007fff5fbfbec0, p=<unavailable>, ec=0x0000000000000000)
>>+ 339
>> frame #6: 0x000000011260b6a7
>>libRemusServer.dylib`boost::filesystem::directory_iterator::directory_ite
>>rator(this=0x00007fff5fbfbec0, p=0x00007fff5fbfc128) + 103 at
>>operations.hpp:793
>> frame #7: 0x0000000112602d5d
>>libRemusServer.dylib`boost::filesystem::directory_iterator::directory_ite
>>rator(this=0x00007fff5fbfbec0, p=0x00007fff5fbfc128) + 29 at
>>operations.hpp:793
>> frame #8: 0x00000001126014df
>>libRemusServer.dylib`remus::server::detail::WorkerFinder::parseDirectory(
>>this=0x00007fff5fbfc370, dir=0x00007fff5fbfc128) + 95 at
>>WorkerFinder.cxx:55
>> frame #9: 0x0000000112601388
>>libRemusServer.dylib`remus::server::detail::WorkerFinder::WorkerFinder(th
>>is=0x00007fff5fbfc370, parser=0x0000000120cb6138,
>>ext=0x0000000120cb6120) + 648 at WorkerFinder.cxx:35
>> frame #10: 0x0000000112601dd5
>>libRemusServer.dylib`remus::server::detail::WorkerFinder::WorkerFinder(th
>>is=0x00007fff5fbfc370, parser=0x0000000120cb6138,
>>ext=0x0000000120cb6120) + 37 at WorkerFinder.cxx:36
>> frame #11: 0x000000011264502b
>>libRemusServer.dylib`remus::server::WorkerFactory::WorkerFactory(this=0x0
>>000000120cb60e0) + 331 at WorkerFactory.cxx:185
>> frame #12: 0x00000001126452a5
>>libRemusServer.dylib`remus::server::WorkerFactory::WorkerFactory(this=0x0
>>000000120cb60e0) + 21 at WorkerFactory.cxx:191
>> frame #13: 0x00000001017e15d8
>>libvtkCMBMeshing-6.3.1.dylib`vtkCMBMeshServerLauncher::vtkCMBMeshServerLa
>>uncher(this=0x0000000120cb6080) + 136 at vtkCMBMeshServerLauncher.cxx:129
>> frame #14: 0x00000001017e1545
>>libvtkCMBMeshing-6.3.1.dylib`vtkCMBMeshServerLauncher::vtkCMBMeshServerLa
>>uncher(this=0x0000000120cb6080) + 21 at vtkCMBMeshServerLauncher.cxx:151
>> frame #15: 0x00000001017e14fa
>>libvtkCMBMeshing-6.3.1.dylib`vtkCMBMeshServerLauncher::New() + 42 at
>>vtkCMBMeshServerLauncher.cxx:121
>> frame #16: 0x0000000100dd1841
>>libCMB_Plugin.dylib`vtkCMBMeshServerLauncherClientServerNewCommand((null)
>>=0x0000000000000000) + 17 at vtkCMBMeshServerLauncherClientServer.cxx:13
>> frame #17: 0x000000010cf7c1e3
>>libvtkClientServer-pv4.3.1.dylib`vtkClientServerInterpreter::NewInstance(
>>this=0x00000001128660a0, classname=0x0000000120d97f70) + 659 at
>>vtkClientServerInterpreter.cxx:1068
>> frame #18: 0x000000010a0a801b
>>libvtkPVServerImplementationCore-pv4.3.1.dylib`vtkSIProxy::CreateVTKObjec
>>ts(this=0x0000000120cb5d30, message=0x00007fff5fbfdde8) + 5403 at
>>vtkSIProxy.cxx:306
>> frame #19: 0x000000010a0a4298
>>libvtkPVServerImplementationCore-pv4.3.1.dylib`vtkSIProxy::Push(this=0x00
>>00000120cb5d30, message=0x00007fff5fbfdde8) + 72 at vtkSIProxy.cxx:115
>> frame #20: 0x000000010a04c4fe
>>libvtkPVServerImplementationCore-pv4.3.1.dylib`vtkPVSessionCore::PushStat
>>eInternal(this=0x0000000112866030, message=0x00007fff5fbfdde8) + 4270 at
>>vtkPVSessionCore.cxx:486
>> frame #21: 0x000000010a04c79f
>>libvtkPVServerImplementationCore-pv4.3.1.dylib`vtkPVSessionCore::PushStat
>>e(this=0x0000000112866030, message=0x00007fff5fbfdde8) + 623 at
>>vtkPVSessionCore.cxx:529
>> frame #22: 0x000000010a046e6a
>>libvtkPVServerImplementationCore-pv4.3.1.dylib`vtkPVSessionBase::PushStat
>>e(this=0x0000000117045210, msg=0x00007fff5fbfdde8) + 74 at
>>vtkPVSessionBase.cxx:142
>> frame #23: 0x0000000109d68dbf
>>libvtkPVServerManagerCore-pv4.3.1.dylib`vtkSMSession::PushState(this=0x00
>>00000117045210, msg=0x00007fff5fbfdde8) + 63 at vtkSMSession.cxx:135
>> frame #24: 0x0000000109d58609
>>libvtkPVServerManagerCore-pv4.3.1.dylib`vtkSMRemoteObject::PushState(this
>>=0x0000000120cb44b0, msg=0x00007fff5fbfdde8) + 169 at
>>vtkSMRemoteObject.cxx:137
>> frame #25: 0x0000000109ce774f
>>libvtkPVServerManagerCore-pv4.3.1.dylib`vtkSMProxy::CreateVTKObjects(this
>>=0x0000000120cb44b0) + 4735 at vtkSMProxy.cxx:788
>> frame #26: 0x0000000109ce5089
>>libvtkPVServerManagerCore-pv4.3.1.dylib`vtkSMProxy::UpdateVTKObjects(this
>>=0x0000000120cb44b0) + 41 at vtkSMProxy.cxx:600
>> frame #27: 0x000000010036bd76
>>libcmbAppCommon.dylib`qtCMBMeshingMonitor::launchLocalMeshServer() + 134
>>at qtCMBMeshingMonitor.cxx:236
>> frame #28: 0x0000000100323cbe
>>libcmbAppCommon.dylib`pqCMBCommonMainWindowCore::launchLocalMeshingServic
>>e(this=0x00000001128ab220) + 62 at pqCMBCommonMainWindowCore.cxx:661
>> frame #29: 0x0000000100028870
>>ModelBuilder`pqCMBModelBuilderMainWindow::initializeApplication(this=0x00
>>00000112e05200) + 5888 at pqCMBModelBuilderMainWindow.cxx:257
>> frame #30: 0x0000000100027096
>>ModelBuilder`pqCMBModelBuilderMainWindow::pqCMBModelBuilderMainWindow(thi
>>s=0x0000000112e05200) + 134 at pqCMBModelBuilderMainWindow.cxx:141
>> frame #31: 0x0000000100029a65
>>ModelBuilder`pqCMBModelBuilderMainWindow::pqCMBModelBuilderMainWindow(thi
>>s=0x0000000112e05200) + 21 at pqCMBModelBuilderMainWindow.cxx:150
>> frame #32: 0x0000000100025533
>>ModelBuilder`pqModelBuilderInitializer::Initialize(this=0x00007fff5fbff81
>>0, argc=1, argv=0x00007fff5fbff898) + 1395 at
>>pqModelBuilderInitializer.cxx:128
>> frame #33: 0x0000000100024bb3 ModelBuilder`main(argc=1,
>>argv=0x00007fff5fbff898) + 371 at ModelBuilder_main.cxx:107
>> frame #34: 0x00007fff8adf05fd libdyld.dylib`start + 1
>> frame #35: 0x00007fff8adf05fd libdyld.dylib`start + 1
>
More information about the Cmb-users
mailing list