Re: [CsMain] Problem with CS Walktest.app on Snow Leopard

[Nicolas Goles]

Res, The crash happens always at the same exact point. I will try to run walktest with a debugger later, I saw similar behavior in this forum post: http://www.crystalspace3d.org/forum/index.php?topic=2008.0 ( At the end of the post, they talk about a very similar crash ) but no answer is provided. Hope someone can help. _Nicolas Goles Domic res February 14, 2011 8:33 AM Is the crash reproduceable? That is, does it always crash at the _same_ point? Also, run walktest with a debugger; it can provide additional information which is helpful for tracking down the problem (such as the arguments to the crashing function). -f.r. ------------------------------------------------------------------------------ The ultimate all-in-one performance toolkit: Intel(R) Parallel Studio XE: Pinpoint memory and threading errors before they happen. Find and fix more than 250 security defects in the development cycle. Locate bottlenecks in serial and parallel code that limit performance. http://p.sf.net/sfu/intel-dev2devfeb _______________________________________________ Crystal-main mailing list Crystal-main@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/crystal-main Unsubscribe: mailto:crystal-main-requ...@lists.sourceforge.net?subject=unsubscribe Nicolas Goles February 13, 2011 11:41 PM Hello!, I'm having a problem with the Walktest.app on Snow Leopard 10.6.6, I got CS to build and the walktest.app also appears to be built correctly, however, when I open the walktest.app it crashes on a particular thread, this is the stack trace. Thread 10 Crashed: 0   walktest                          0x000000010009571e csPluginManager::LoadPluginInstance(char const*, unsigned int) + 1870 1   shaderweaver.csbundle             0x00000001183ec9d8 CS::Plugin::ShaderWeaver::Synthesizer::SynthesizeTechnique::operator()(CS::Plugin::ShaderWeaver::ShaderVarNodesHelper&, iDocumentNode*, CS::Plugin::ShaderWeaver::Snippet const*, CS::Plugin::ShaderWeaver::TechniqueGraph const&) + 2232 (plugin.h:263) 2   shaderweaver.csbundle             0x00000001183fb935 CS::Plugin::ShaderWeaver::Synthesizer::SynthesizeTechnique::Run() + 37 (synth.h:192) 3   shaderweaver.csbundle             0x000000011842d003 CS::Threading::ThreadedJobQueue::QueueRunnable::Run() + 691 4   shaderweaver.csbundle             0x0000000118449629 CS::Threading::Implementation::(anonymous namespace)::proxyFunc(void*) + 185 5   libSystem.B.dylib                 0x00007fff8358c536 _pthread_start + 331 6   libSystem.B.dylib                 0x00007fff8358c3e9 thread_start + 13 I attached the full stack trace too, if someone finds it helpful. Any ideas ? _Nicolas Goles Domic res February 14, 2011 8:33 AM Is the crash reproduceable? That is, does it always crash at the _same_ point? Also, run walktest with a debugger; it can provide additional information which is helpful for tracking down the problem (such as the arguments to the crashing function). -f.r. ------------------------------------------------------------------------------ The ultimate all-in-one performance toolkit: Intel(R) Parallel Studio XE: Pinpoint memory and threading errors before they happen. Find and fix more than 250 security defects in the development cycle. Locate bottlenecks in serial and parallel code that limit performance. http://p.sf.net/sfu/intel-dev2devfeb _______________________________________________ Crystal-main mailing list Crystal-main@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/crystal-main Unsubscribe: mailto:crystal-main-requ...@lists.sourceforge.net?subject=unsubscribe Nicolas Goles February 13, 2011 11:41 PM Hello!, I'm having a problem with the Walktest.app on Snow Leopard 10.6.6, I got CS to build and the walktest.app also appears to be built correctly, however, when I open the walktest.app it crashes on a particular thread, this is the stack trace. Thread 10 Crashed: 0   walktest                          0x000000010009571e csPluginManager::LoadPluginInstance(char const*, unsigned int) + 1870 1   shaderweaver.csbundle             0x00000001183ec9d8 CS::Plugin::ShaderWeaver::Synthesizer::SynthesizeTechnique::operator()(CS::Plugin::ShaderWeaver::ShaderVarNodesHelper&, iDocumentNode*, CS::Plugin::ShaderWeaver::Snippet const*, CS::Plugin::ShaderWeaver::TechniqueGraph const&) + 2232 (plugin.h:263) 2   shaderweaver.csbundle             0x00000001183fb935 CS::Plugin::ShaderWeaver::Synthesizer::SynthesizeTechnique::Run() + 37 (synth.h:192) 3   shaderweaver.csbundle             0x000000011842d003 CS::Threading::ThreadedJobQueue::QueueRunnable::Run() + 691 4   shaderweaver.csbundle             0x0000000118449629 CS::Threading::Implementation::(anonymous namespace)::proxyFunc(void*) + 185 5   libSystem.B.dylib                 0x00007fff8358c536 _pthread_start + 331 6   libSystem.B.dylib                 0x00007fff8358c3e9 thread_start + 13 I attached the full stack trace too, if someone finds it helpful. Any ideas ? _Nicolas Goles Domic

------------------------------------------------------------------------------
The ultimate all-in-one performance toolkit: Intel(R) Parallel Studio XE:
Pinpoint memory and threading errors before they happen.
Find and fix more than 250 security defects in the development cycle.
Locate bottlenecks in serial and parallel code that limit performance.
http://p.sf.net/sfu/intel-dev2devfeb
_______________________________________________
Crystal-main mailing list
Crystal-main@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/crystal-main
Unsubscribe: 
mailto:crystal-main-requ...@lists.sourceforge.net?subject=unsubscribe