From bob.obara at kitware.com Wed Jun 3 17:17:35 2015 From: bob.obara at kitware.com (Robert Michael O'Bara) Date: Wed, 3 Jun 2015 17:17:35 -0400 Subject: [Cmb-users] Error starting CMB v4 from superbuild In-Reply-To: References: Message-ID: Hi Amanda, Have you tried building with the clang compiler in XCode? Bob Robert M. O'Bara, MEng. Assistant Director of Scientific Computing Kitware Inc. 28 Corporate Drive Suite 101 Clifton Park, NY 12065 Phone: (518) 881- 4931 > On Jun 3, 2015, at 5:16 PM, Hines, Amanda M ERDC-RDE-ITL-MS wrote: > > I built CMB v4 using the superbuild (commit c327786588dbaa9295daa6c283a58d7cb6f45e53) and am getting a segmentation fault when trying to run ModelBuilder. I am running on Mac 10.9.5 with brew installed gcc 4.8.4. Here is the error I get when trying to run ModelBuilder: > zsh: segmentation fault ./ModelBuilder.app/Contents/MacOS/ModelBuilder > > I tried running it through gdb and get the following error: > > Program received signal SIGSEGV, Segmentation fault. > 0x00007fff8a58e2ff in legacyToXMPArray () from /usr/lib/libobjc.A.dylib > > (gdb) where > #0 0x00007fff8a58e2ff in legacyToXMPArray () from /usr/lib/libobjc.A.dylib > #1 0x00007fff8a58f53a in typeinfo for _MPExtension () from /usr/lib/libobjc.A.dylib > #2 0x00007fff8a590446 in internal_little2_encoding_ns () from /usr/lib/libobjc.A.dylib > #3 0x000000268a5ad851 in ?? () > #4 0x00007fff5fbf8eb0 in ?? () > #5 0x0000000109469750 in ?? () > from /Users/rditlaem/Work/Applications/cmb_v4/build_gcc/paraview/src/paraview-build/lib/libvtkRenderingOpenGL-pv4.3.1.dylib > #6 0x00000006772e9818 in ?? () > #7 0x0000002900bf8e20 in ?? () > #8 0x0000000000000000 in ?? () > > Here is a print out of my environment in case it is an environment problem. > > TMPDIR=/var/folders/34/qw55shds7r3_pzmjph0qn_04ckzhmq/T/ > Apple_PubSub_Socket_Render=/tmp/launch-Xbl7tL/Render > TERM=xterm-256color > LANG=en_US.UTF-8 > DISPLAY=/tmp/launch-Xwg3Az/org.macosforge.xquartz:0 > SSH_AUTH_SOCK=/tmp/launch-YW9vuc/Listeners > TERM_PROGRAM=Apple_Terminal > __CHECKFIX1436934=1 > TERM_PROGRAM_VERSION=326 > SHELL=/bin/bash > PATH=/usr/local/bin:/usr/bin:/bin:/usr/sbin:/sbin:/usr/local/bin:/opt/X11/bin > SHLVL=1 > PROMPT=[%c]%# > CLICOLOR=1 > LSCOLORS=ExFxCxDxBxegedabagacad > CC=/usr/local/bin/gcc > CXX=/usr/local/bin/g++ > _=/usr/bin/printenv > > Thanks, > Amanda > -------------- next part -------------- An HTML attachment was scrubbed... URL: From bob.obara at kitware.com Thu Jun 4 14:55:50 2015 From: bob.obara at kitware.com (Robert Michael O'Bara) Date: Thu, 4 Jun 2015 14:55:50 -0400 Subject: [Cmb-users] Error starting CMB v4 from superbuild In-Reply-To: References: Message-ID: Hi Amanda, You are setting a DYLD_LIBRARY_PATH variable before running ModelBuilder in the case of clang? When running the clang version through lldb what does the stack look like? Bob Robert M. O'Bara, MEng. Assistant Director of Scientific Computing Kitware Inc. 28 Corporate Drive Suite 101 Clifton Park, NY 12065 Phone: (518) 881- 4931 > On Jun 3, 2015, at 5:28 PM, Hines, Amanda M ERDC-RDE-ITL-MS wrote: > > Yep, with clang I get the following error: > > > Find Session cmb_forwarding > Find Session discrete > Find Session exodus > Find Session native > Find Session remus_remote > zsh: segmentation fault ./ModelBuilder.app/Contents/MacOS/ModelBuilder > > From: Bob O'Bara > > Date: Wednesday, June 3, 2015 at 4:17 PM > To: Amanda Hines > > Cc: "cmb-users at computationalmodelbuilder.org " > > Subject: Re: Error starting CMB v4 from superbuild > > Hi Amanda, > > Have you tried building with the clang compiler in XCode? > > Bob > > Robert M. O'Bara, MEng. > Assistant Director of Scientific Computing > > Kitware Inc. > 28 Corporate Drive > Suite 101 > Clifton Park, NY 12065 > > Phone: (518) 881- 4931 > > > > >> On Jun 3, 2015, at 5:16 PM, Hines, Amanda M ERDC-RDE-ITL-MS > wrote: >> >> I built CMB v4 using the superbuild (commit c327786588dbaa9295daa6c283a58d7cb6f45e53) and am getting a segmentation fault when trying to run ModelBuilder. I am running on Mac 10.9.5 with brew installed gcc 4.8.4. Here is the error I get when trying to run ModelBuilder: >> zsh: segmentation fault ./ModelBuilder.app/Contents/MacOS/ModelBuilder >> >> I tried running it through gdb and get the following error: >> >> Program received signal SIGSEGV, Segmentation fault. >> 0x00007fff8a58e2ff in legacyToXMPArray () from /usr/lib/libobjc.A.dylib >> >> (gdb) where >> #0 0x00007fff8a58e2ff in legacyToXMPArray () from /usr/lib/libobjc.A.dylib >> #1 0x00007fff8a58f53a in typeinfo for _MPExtension () from /usr/lib/libobjc.A.dylib >> #2 0x00007fff8a590446 in internal_little2_encoding_ns () from /usr/lib/libobjc.A.dylib >> #3 0x000000268a5ad851 in ?? () >> #4 0x00007fff5fbf8eb0 in ?? () >> #5 0x0000000109469750 in ?? () >> from /Users/rditlaem/Work/Applications/cmb_v4/build_gcc/paraview/src/paraview-build/lib/libvtkRenderingOpenGL-pv4.3.1.dylib >> #6 0x00000006772e9818 in ?? () >> #7 0x0000002900bf8e20 in ?? () >> #8 0x0000000000000000 in ?? () >> >> Here is a print out of my environment in case it is an environment problem. >> >> TMPDIR=/var/folders/34/qw55shds7r3_pzmjph0qn_04ckzhmq/T/ >> Apple_PubSub_Socket_Render=/tmp/launch-Xbl7tL/Render >> TERM=xterm-256color >> LANG=en_US.UTF-8 >> DISPLAY=/tmp/launch-Xwg3Az/org.macosforge.xquartz:0 >> SSH_AUTH_SOCK=/tmp/launch-YW9vuc/Listeners >> TERM_PROGRAM=Apple_Terminal >> __CHECKFIX1436934=1 >> TERM_PROGRAM_VERSION=326 >> SHELL=/bin/bash >> PATH=/usr/local/bin:/usr/bin:/bin:/usr/sbin:/sbin:/usr/local/bin:/opt/X11/bin >> SHLVL=1 >> PROMPT=[%c]%# >> CLICOLOR=1 >> LSCOLORS=ExFxCxDxBxegedabagacad >> CC=/usr/local/bin/gcc >> CXX=/usr/local/bin/g++ >> _=/usr/bin/printenv >> >> Thanks, >> Amanda >> > -------------- next part -------------- An HTML attachment was scrubbed... URL: From david.thompson at kitware.com Fri Jun 5 15:33:09 2015 From: david.thompson at kitware.com (David Thompson) Date: Fri, 5 Jun 2015 15:33:09 -0400 Subject: [Cmb-users] Error starting CMB v4 from superbuild In-Reply-To: <122DD5E2-611E-4DCF-A774-1391A699364D@kitware.com> References: <122DD5E2-611E-4DCF-A774-1391A699364D@kitware.com> Message-ID: 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.dylib >>> 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/ModelBuilder.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 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 const&) (.part.23) + 3 > libstdc++.6.dylib`std::string::_Rep::_M_dispose(std::allocator 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 const&) (.part.23) + 17 > > And the backtrace from lldb: > > * thread #1: tid = 0x97ab9, 0x000000011247e5f9 libstdc++.6.dylib`std::string::_Rep::_M_dispose(std::allocator 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 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_construct(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_construct(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_construct(boost::filesystem::directory_iterator&, boost::filesystem::path const&, boost::system::error_code*) [inlined] boost::filesystem::directory_entry::assign(symlink_st=, st=, p=0x00007fff5fbfbcb0, this=0x00000001211d3d40) > frame #5: 0x00000001123e4cf3 libboost_filesystem.dylib`boost::filesystem::detail::directory_iterator_construct(it=0x00007fff5fbfbec0, p=, ec=0x0000000000000000) + 339 > frame #6: 0x000000011260b6a7 libRemusServer.dylib`boost::filesystem::directory_iterator::directory_iterator(this=0x00007fff5fbfbec0, p=0x00007fff5fbfc128) + 103 at operations.hpp:793 > frame #7: 0x0000000112602d5d libRemusServer.dylib`boost::filesystem::directory_iterator::directory_iterator(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(this=0x00007fff5fbfc370, parser=0x0000000120cb6138, ext=0x0000000120cb6120) + 648 at WorkerFinder.cxx:35 > frame #10: 0x0000000112601dd5 libRemusServer.dylib`remus::server::detail::WorkerFinder::WorkerFinder(this=0x00007fff5fbfc370, parser=0x0000000120cb6138, ext=0x0000000120cb6120) + 37 at WorkerFinder.cxx:36 > frame #11: 0x000000011264502b libRemusServer.dylib`remus::server::WorkerFactory::WorkerFactory(this=0x0000000120cb60e0) + 331 at WorkerFactory.cxx:185 > frame #12: 0x00000001126452a5 libRemusServer.dylib`remus::server::WorkerFactory::WorkerFactory(this=0x0000000120cb60e0) + 21 at WorkerFactory.cxx:191 > frame #13: 0x00000001017e15d8 libvtkCMBMeshing-6.3.1.dylib`vtkCMBMeshServerLauncher::vtkCMBMeshServerLauncher(this=0x0000000120cb6080) + 136 at vtkCMBMeshServerLauncher.cxx:129 > frame #14: 0x00000001017e1545 libvtkCMBMeshing-6.3.1.dylib`vtkCMBMeshServerLauncher::vtkCMBMeshServerLauncher(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::CreateVTKObjects(this=0x0000000120cb5d30, message=0x00007fff5fbfdde8) + 5403 at vtkSIProxy.cxx:306 > frame #19: 0x000000010a0a4298 libvtkPVServerImplementationCore-pv4.3.1.dylib`vtkSIProxy::Push(this=0x0000000120cb5d30, message=0x00007fff5fbfdde8) + 72 at vtkSIProxy.cxx:115 > frame #20: 0x000000010a04c4fe libvtkPVServerImplementationCore-pv4.3.1.dylib`vtkPVSessionCore::PushStateInternal(this=0x0000000112866030, message=0x00007fff5fbfdde8) + 4270 at vtkPVSessionCore.cxx:486 > frame #21: 0x000000010a04c79f libvtkPVServerImplementationCore-pv4.3.1.dylib`vtkPVSessionCore::PushState(this=0x0000000112866030, message=0x00007fff5fbfdde8) + 623 at vtkPVSessionCore.cxx:529 > frame #22: 0x000000010a046e6a libvtkPVServerImplementationCore-pv4.3.1.dylib`vtkPVSessionBase::PushState(this=0x0000000117045210, msg=0x00007fff5fbfdde8) + 74 at vtkPVSessionBase.cxx:142 > frame #23: 0x0000000109d68dbf libvtkPVServerManagerCore-pv4.3.1.dylib`vtkSMSession::PushState(this=0x0000000117045210, 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::launchLocalMeshingService(this=0x00000001128ab220) + 62 at pqCMBCommonMainWindowCore.cxx:661 > frame #29: 0x0000000100028870 ModelBuilder`pqCMBModelBuilderMainWindow::initializeApplication(this=0x0000000112e05200) + 5888 at pqCMBModelBuilderMainWindow.cxx:257 > frame #30: 0x0000000100027096 ModelBuilder`pqCMBModelBuilderMainWindow::pqCMBModelBuilderMainWindow(this=0x0000000112e05200) + 134 at pqCMBModelBuilderMainWindow.cxx:141 > frame #31: 0x0000000100029a65 ModelBuilder`pqCMBModelBuilderMainWindow::pqCMBModelBuilderMainWindow(this=0x0000000112e05200) + 21 at pqCMBModelBuilderMainWindow.cxx:150 > frame #32: 0x0000000100025533 ModelBuilder`pqModelBuilderInitializer::Initialize(this=0x00007fff5fbff810, 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 From Amanda.M.Hines at erdc.dren.mil Mon Jun 8 12:07:20 2015 From: Amanda.M.Hines at erdc.dren.mil (Hines, Amanda M ERDC-RDE-ITL-MS) Date: Mon, 8 Jun 2015 16:07:20 +0000 Subject: [Cmb-users] Error starting CMB v4 from superbuild In-Reply-To: References: <122DD5E2-611E-4DCF-A774-1391A699364D@kitware.com> Message-ID: 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" 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 >>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 >>const&) (.part.23) + 3 >> libstdc++.6.dylib`std::string::_Rep::_M_dispose(std::allocator >>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 const&) (.part.23) + >>17 >> >> And the backtrace from lldb: >> >> * thread #1: tid = 0x97ab9, 0x000000011247e5f9 >>libstdc++.6.dylib`std::string::_Rep::_M_dispose(std::allocator >>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 >>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=, >>st=, p=0x00007fff5fbfbcb0, this=0x00000001211d3d40) >> frame #5: 0x00000001123e4cf3 >>libboost_filesystem.dylib`boost::filesystem::detail::directory_iterator_c >>onstruct(it=0x00007fff5fbfbec0, p=, 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 > From david.thompson at kitware.com Mon Jun 8 12:23:39 2015 From: david.thompson at kitware.com (David Thompson) Date: Mon, 8 Jun 2015 12:23:39 -0400 Subject: [Cmb-users] Error starting CMB v4 from superbuild In-Reply-To: References: <122DD5E2-611E-4DCF-A774-1391A699364D@kitware.com> Message-ID: Hi Amanda, > 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 > -> 35 this->parseDirectory(cwd); > (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). There are at least 2 ways boost libraries can get confused: 1. Run-time selection of a different boost from the one used during compilation. 2. Build-time compilation of different libraries against different boost libraries (i.e., headers from one boost used but the application linked to another). The former usually prints messages to the terminal when different dependent libraries ask the linker to load multiple versions of the same library. But to double-check, you can run "image list" in lldb and verify that (a) there is only one version of boost_filesystem and (b) it is the correct boost for your application. The latter can be more subtle. If "image list" seems correct, then you might verify that your Remus, SMTK, and CMB build directories all have CMakeCache.txt references to Boost pointing to the same boost *and* that the include-directory paths match the Boost_FILESYSTEM_LIBRARY_* paths. David From robert.maynard at kitware.com Mon Jun 8 13:24:52 2015 From: robert.maynard at kitware.com (Robert Maynard) Date: Mon, 8 Jun 2015 13:24:52 -0400 Subject: [Cmb-users] Error starting CMB v4 from superbuild In-Reply-To: References: <122DD5E2-611E-4DCF-A774-1391A699364D@kitware.com> Message-ID: This smells like a mismatch of boost versions. On Mon, Jun 8, 2015 at 12:23 PM, David Thompson wrote: > Hi Amanda, > >> 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 >> -> 35 this->parseDirectory(cwd); >> (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). > > There are at least 2 ways boost libraries can get confused: > > 1. Run-time selection of a different boost from the one used during compilation. > 2. Build-time compilation of different libraries against different boost libraries (i.e., headers from one boost used but the application linked to another). > > The former usually prints messages to the terminal when different dependent libraries ask the linker to load multiple versions of the same library. But to double-check, you can run "image list" in lldb and verify that (a) there is only one version of boost_filesystem and (b) it is the correct boost for your application. > > The latter can be more subtle. If "image list" seems correct, then you might verify that your Remus, SMTK, and CMB build directories all have CMakeCache.txt references to Boost pointing to the same boost *and* that the include-directory paths match the Boost_FILESYSTEM_LIBRARY_* paths. > > David From david.thompson at kitware.com Fri Jun 12 11:52:47 2015 From: david.thompson at kitware.com (David Thompson) Date: Fri, 12 Jun 2015 11:52:47 -0400 Subject: [Cmb-users] Dashboard problems Message-ID: <240C0828-75C4-4FE3-B470-92750C443B85@kitware.com> Hi all, It looks like the CMB superbuild is having some new issues but I don't see any new merges. Does anyone know what's up? The continuous and coverage SMTK builds that use the superbuild Boost and ParaView are complaining that they cannot be found: https://www.kitware.com/CDash/viewConfigure.php?buildid=561280 Thanks, David From damian at sourceryinstitute.org Tue Jun 16 00:10:06 2015 From: damian at sourceryinstitute.org (Damian Rouson) Date: Mon, 15 Jun 2015 21:10:06 -0700 Subject: [Cmb-users] Evaluating CMB with Gambit files from a legacy project Message-ID: All, We are attempting to evaluate the use of CMB to build models for a new project that builds upon the legacy multiphysics solver framework NEMO (http://www.ce.uniroma2.it/nemo/) circa 2006. As a first step, I installed CMB and attempted to read two Gambit version 2.2.30 files from NEMO?s applications/examples/mesh subdirectory. When I select either file, CMB reports ?More than one reader? found? and I choose the Gambit reader. I am then met with a blank CMB window ? no images and no messages regarding whether the file was read successfully. I?m not sure if this mailing list accepts attachments so I have placed the files on Dropbox at https://dl.dropboxusercontent.com/u/7038972/gambit/cylinder_tet.neu https://dl.dropboxusercontent.com/u/7038972/gambit/cylinder_hyb.neu Any advice would be very much appreciated. ________________________________ Damian Rouson, Ph.D., P.E. Founder & President, Sourcery, Inc. 510-600-2992 (mobile) http://www.sourceryinstitute.org http://rouson.youcanbook.me From yumin.yuan at kitware.com Thu Jun 18 15:38:45 2015 From: yumin.yuan at kitware.com (Yumin Yuan) Date: Thu, 18 Jun 2015 15:38:45 -0400 Subject: [Cmb-users] Error starting CMB v4 from superbuild In-Reply-To: References: <122DD5E2-611E-4DCF-A774-1391A699364D@kitware.com> Message-ID: Hi Amanda, Not sure if this is the same cause for your problem, but I just encountered the same problem for my cmb build when I start building the meshing support. Basically, the boost::filesystem::current_path() returns an empty path, and it crashed while trying to parse the empty path. Rob (and Dave) helped me to figure out what's the root cause of the problem. I have a 10.10 machine and I set the build target to 10.8 in the superbuild. In this scenario, all the libraries in cmb/smtk and their dependencies will link against libstdc++, except boost libraries, which will link against libc++, and the mixed linking of libstdc++ and libc++ causes the crash. Setting target to 10.9 and 10.10 does not have this problem, and I will file an issue with cmbsuperbuild for this bug. Yumin On Mon, Jun 8, 2015 at 1:24 PM, Robert Maynard wrote: > This smells like a mismatch of boost versions. > > On Mon, Jun 8, 2015 at 12:23 PM, David Thompson > wrote: > > Hi Amanda, > > > >> 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 > >> -> 35 this->parseDirectory(cwd); > >> (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). > > > > There are at least 2 ways boost libraries can get confused: > > > > 1. Run-time selection of a different boost from the one used during > compilation. > > 2. Build-time compilation of different libraries against different boost > libraries (i.e., headers from one boost used but the application linked to > another). > > > > The former usually prints messages to the terminal when different > dependent libraries ask the linker to load multiple versions of the same > library. But to double-check, you can run "image list" in lldb and verify > that (a) there is only one version of boost_filesystem and (b) it is the > correct boost for your application. > > > > The latter can be more subtle. If "image list" seems correct, then you > might verify that your Remus, SMTK, and CMB build directories all have > CMakeCache.txt references to Boost pointing to the same boost *and* that > the include-directory paths match the Boost_FILESYSTEM_LIBRARY_* paths. > > > > David > _______________________________________________ > Cmb-users mailing list > Cmb-users at computationalmodelbuilder.org > http://public.kitware.com/mailman/listinfo/cmb-users > -------------- next part -------------- An HTML attachment was scrubbed... URL: From yumin.yuan at kitware.com Thu Jun 18 17:18:06 2015 From: yumin.yuan at kitware.com (Yumin Yuan) Date: Thu, 18 Jun 2015 17:18:06 -0400 Subject: [Cmb-users] Evaluating CMB with Gambit files from a legacy project In-Reply-To: References: Message-ID: Hi Damian, CMB (ModelBuilder) does not support Gambit file directly. However, if you can convert them to vtk file, CMB should be able to load the vtk files. Paraview does have a Gambit reader, and I tried to load the two files into paraview, but they failed to load too. I did not investigate why these files can't be loaded into Paraview, and I am guessing some mismatch between the file version and the reader. In short, when loading vtk files, CMB will try to do a surface extraction if it is a volume, and use the surface to build a B-rep for the model. If there is a "Material" cell array with the vtk data, the surface will be partitioned using the "Material" array. Like paraview, CMB also has plugin architecture and can be extended to support more type of meshes through plugin. HTH, Yumin On Tue, Jun 16, 2015 at 12:10 AM, Damian Rouson < damian at sourceryinstitute.org> wrote: > All, > > We are attempting to evaluate the use of CMB to build models for a new > project that builds upon the legacy multiphysics solver framework NEMO ( > http://www.ce.uniroma2.it/nemo/) circa 2006. As a first step, I > installed CMB and attempted to read two Gambit version 2.2.30 files from > NEMO?s applications/examples/mesh subdirectory. When I select either > file, CMB reports ?More than one reader? found? and I choose the Gambit > reader. I am then met with a blank CMB window ? no images and no messages > regarding whether the file was read successfully. > > I?m not sure if this mailing list accepts attachments so I have placed the > files on Dropbox at > > https://dl.dropboxusercontent.com/u/7038972/gambit/cylinder_tet.neu > https://dl.dropboxusercontent.com/u/7038972/gambit/cylinder_hyb.neu > > Any advice would be very much appreciated. > > ________________________________ > Damian Rouson, Ph.D., P.E. > Founder & President, Sourcery, Inc. > 510-600-2992 (mobile) > http://www.sourceryinstitute.org > http://rouson.youcanbook.me > > _______________________________________________ > Cmb-users mailing list > Cmb-users at computationalmodelbuilder.org > http://public.kitware.com/mailman/listinfo/cmb-users > -------------- next part -------------- An HTML attachment was scrubbed... URL: From bob.obara at kitware.com Fri Jun 26 16:48:15 2015 From: bob.obara at kitware.com (Robert Michael O'Bara) Date: Fri, 26 Jun 2015 16:48:15 -0400 Subject: [Cmb-users] Model Builder crash In-Reply-To: References: Message-ID: Hi Amanda, I'm off today. I've forwarded this to the mailing list. We will get back to you on this on as soon as we can. Bob Sent from my iPad > On Jun 26, 2015, at 3:32 PM, Hines, Amanda M ERDC-RDE-ITL-MS wrote: > > Hey Bob, > > I?m getting a Model Builder crash when I try to type more than one character in a multiline string attribute in SimBuilder. I haven?t tested this before so I am not sure if this is a new bug or if it?s been there for awhile. > > Thanks, > Amanda From yumin.yuan at kitware.com Fri Jun 26 17:12:36 2015 From: yumin.yuan at kitware.com (Yumin Yuan) Date: Fri, 26 Jun 2015 17:12:36 -0400 Subject: [Cmb-users] Model Builder crash In-Reply-To: References: Message-ID: Hi Amanda, I have a fix for this (PR#216 ), and am waiting for dashboards to give green lights to merge it. I will move smtk release-v1 branch to include this fix after it is merged in. Yumin On Fri, Jun 26, 2015 at 4:48 PM, Robert Michael O'Bara < bob.obara at kitware.com> wrote: > Hi Amanda, > > I'm off today. I've forwarded this to the mailing list. We will get > back to you on this on as soon as we can. > > Bob > > Sent from my iPad > > > On Jun 26, 2015, at 3:32 PM, Hines, Amanda M ERDC-RDE-ITL-MS < > Amanda.M.Hines at erdc.dren.mil> wrote: > > > > Hey Bob, > > > > I?m getting a Model Builder crash when I try to type more than one > character in a multiline string attribute in SimBuilder. I haven?t tested > this before so I am not sure if this is a new bug or if it?s been there for > awhile. > > > > Thanks, > > Amanda > _______________________________________________ > Cmb-users mailing list > Cmb-users at computationalmodelbuilder.org > http://public.kitware.com/mailman/listinfo/cmb-users > -------------- next part -------------- An HTML attachment was scrubbed... URL: From Amanda.M.Hines at erdc.dren.mil Fri Jun 26 17:13:47 2015 From: Amanda.M.Hines at erdc.dren.mil (Hines, Amanda M ERDC-RDE-ITL-MS) Date: Fri, 26 Jun 2015 21:13:47 +0000 Subject: [Cmb-users] Model Builder crash In-Reply-To: References: Message-ID: Ok, great. Thanks, Yumin. From: Yumin Yuan > Date: Friday, June 26, 2015 at 4:12 PM To: Bob O'Bara > Cc: Amanda Hines >, cmb-users > Subject: Re: [Cmb-users] Model Builder crash Hi Amanda, I have a fix for this (PR#216), and am waiting for dashboards to give green lights to merge it. I will move smtk release-v1 branch to include this fix after it is merged in. Yumin On Fri, Jun 26, 2015 at 4:48 PM, Robert Michael O'Bara > wrote: Hi Amanda, I'm off today. I've forwarded this to the mailing list. We will get back to you on this on as soon as we can. Bob Sent from my iPad > On Jun 26, 2015, at 3:32 PM, Hines, Amanda M ERDC-RDE-ITL-MS > wrote: > > Hey Bob, > > I?m getting a Model Builder crash when I try to type more than one character in a multiline string attribute in SimBuilder. I haven?t tested this before so I am not sure if this is a new bug or if it?s been there for awhile. > > Thanks, > Amanda _______________________________________________ Cmb-users mailing list Cmb-users at computationalmodelbuilder.org http://public.kitware.com/mailman/listinfo/cmb-users -------------- next part -------------- An HTML attachment was scrubbed... URL: From yumin.yuan at kitware.com Sat Jun 27 13:20:43 2015 From: yumin.yuan at kitware.com (Yumin Yuan) Date: Sat, 27 Jun 2015 13:20:43 -0400 Subject: [Cmb-users] Model Builder crash In-Reply-To: References: Message-ID: Hi Amanda, I merged in the fixes and moved smtk release-v1 to include the following fixes: 1. Crash when typing more than one characters in multiline string attribute item. 2. Meshing will not start again after edge operation. 3. The tree view will not refresh to show the new group when Creating group after edge operation. Best, Yumin On Fri, Jun 26, 2015 at 5:13 PM, Hines, Amanda M ERDC-RDE-ITL-MS < Amanda.M.Hines at erdc.dren.mil> wrote: > Ok, great. Thanks, Yumin. > > From: Yumin Yuan > Date: Friday, June 26, 2015 at 4:12 PM > To: Bob O'Bara > Cc: Amanda Hines , cmb-users < > cmb-users at computationalmodelbuilder.org> > Subject: Re: [Cmb-users] Model Builder crash > > Hi Amanda, > > I have a fix for this (PR#216 ), > and am waiting for dashboards to give green lights to merge it. I will move > smtk release-v1 branch to include this fix after it is merged in. > > Yumin > > On Fri, Jun 26, 2015 at 4:48 PM, Robert Michael O'Bara < > bob.obara at kitware.com> wrote: > >> Hi Amanda, >> >> I'm off today. I've forwarded this to the mailing list. We will get >> back to you on this on as soon as we can. >> >> Bob >> >> Sent from my iPad >> >> > On Jun 26, 2015, at 3:32 PM, Hines, Amanda M ERDC-RDE-ITL-MS < >> Amanda.M.Hines at erdc.dren.mil> wrote: >> > >> > Hey Bob, >> > >> > I?m getting a Model Builder crash when I try to type more than one >> character in a multiline string attribute in SimBuilder. I haven?t tested >> this before so I am not sure if this is a new bug or if it?s been there for >> awhile. >> > >> > Thanks, >> > Amanda >> _______________________________________________ >> Cmb-users mailing list >> Cmb-users at computationalmodelbuilder.org >> http://public.kitware.com/mailman/listinfo/cmb-users >> > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From Amanda.M.Hines at erdc.dren.mil Mon Jun 29 10:45:46 2015 From: Amanda.M.Hines at erdc.dren.mil (Hines, Amanda M ERDC-RDE-ITL-MS) Date: Mon, 29 Jun 2015 14:45:46 +0000 Subject: [Cmb-users] Model Builder crash In-Reply-To: References: Message-ID: Thanks, Yumin. I will pull it and test it today. Thanks, Amanda From: Yumin Yuan > Date: Saturday, June 27, 2015 at 12:20 PM To: Amanda Hines > Cc: Bob O'Bara >, cmb-users > Subject: Re: [Cmb-users] Model Builder crash Hi Amanda, I merged in the fixes and moved smtk release-v1 to include the following fixes: 1. Crash when typing more than one characters in multiline string attribute item. 2. Meshing will not start again after edge operation. 3. The tree view will not refresh to show the new group when Creating group after edge operation. Best, Yumin On Fri, Jun 26, 2015 at 5:13 PM, Hines, Amanda M ERDC-RDE-ITL-MS > wrote: Ok, great. Thanks, Yumin. From: Yumin Yuan > Date: Friday, June 26, 2015 at 4:12 PM To: Bob O'Bara > Cc: Amanda Hines >, cmb-users > Subject: Re: [Cmb-users] Model Builder crash Hi Amanda, I have a fix for this (PR#216), and am waiting for dashboards to give green lights to merge it. I will move smtk release-v1 branch to include this fix after it is merged in. Yumin On Fri, Jun 26, 2015 at 4:48 PM, Robert Michael O'Bara > wrote: Hi Amanda, I'm off today. I've forwarded this to the mailing list. We will get back to you on this on as soon as we can. Bob Sent from my iPad > On Jun 26, 2015, at 3:32 PM, Hines, Amanda M ERDC-RDE-ITL-MS > wrote: > > Hey Bob, > > I?m getting a Model Builder crash when I try to type more than one character in a multiline string attribute in SimBuilder. I haven?t tested this before so I am not sure if this is a new bug or if it?s been there for awhile. > > Thanks, > Amanda _______________________________________________ Cmb-users mailing list Cmb-users at computationalmodelbuilder.org http://public.kitware.com/mailman/listinfo/cmb-users -------------- next part -------------- An HTML attachment was scrubbed... URL: From bob.obara at kitware.com Mon Jun 29 10:48:27 2015 From: bob.obara at kitware.com (Robert Michael O'Bara) Date: Mon, 29 Jun 2015 10:48:27 -0400 Subject: [Cmb-users] Model Builder crash In-Reply-To: References: Message-ID: <0E01F714-ECD2-4822-9F97-AEDB4A3BE9DB@kitware.com> Hi Amanda, Yumin also fixed the bug that prevented the model from being meshed after the edges were split. Bob Robert M. O'Bara, MEng. Assistant Director of Scientific Computing Kitware Inc. 28 Corporate Drive Suite 101 Clifton Park, NY 12065 Phone: (518) 881- 4931 > On Jun 29, 2015, at 10:45 AM, Hines, Amanda M ERDC-RDE-ITL-MS wrote: > > Thanks, Yumin. I will pull it and test it today. > > Thanks, > Amanda > > From: Yumin Yuan > > Date: Saturday, June 27, 2015 at 12:20 PM > To: Amanda Hines > > Cc: Bob O'Bara >, cmb-users > > Subject: Re: [Cmb-users] Model Builder crash > > Hi Amanda, > > I merged in the fixes and moved smtk release-v1 to include the following fixes: > > 1. Crash when typing more than one characters in multiline string attribute item. > 2. Meshing will not start again after edge operation. > 3. The tree view will not refresh to show the new group when Creating group after edge operation. > > Best, > Yumin > > On Fri, Jun 26, 2015 at 5:13 PM, Hines, Amanda M ERDC-RDE-ITL-MS > wrote: >> Ok, great. Thanks, Yumin. >> >> From: Yumin Yuan > >> Date: Friday, June 26, 2015 at 4:12 PM >> To: Bob O'Bara > >> Cc: Amanda Hines >, cmb-users > >> Subject: Re: [Cmb-users] Model Builder crash >> >> Hi Amanda, >> >> I have a fix for this (PR#216 ), and am waiting for dashboards to give green lights to merge it. I will move smtk release-v1 branch to include this fix after it is merged in. >> >> Yumin >> >> On Fri, Jun 26, 2015 at 4:48 PM, Robert Michael O'Bara > wrote: >>> Hi Amanda, >>> >>> I'm off today. I've forwarded this to the mailing list. We will get back to you on this on as soon as we can. >>> >>> Bob >>> >>> Sent from my iPad >>> >>> > On Jun 26, 2015, at 3:32 PM, Hines, Amanda M ERDC-RDE-ITL-MS > wrote: >>> > >>> > Hey Bob, >>> > >>> > I?m getting a Model Builder crash when I try to type more than one character in a multiline string attribute in SimBuilder. I haven?t tested this before so I am not sure if this is a new bug or if it?s been there for awhile. >>> > >>> > Thanks, >>> > Amanda >>> _______________________________________________ >>> Cmb-users mailing list >>> Cmb-users at computationalmodelbuilder.org >>> http://public.kitware.com/mailman/listinfo/cmb-users >> > -------------- next part -------------- An HTML attachment was scrubbed... URL: