On Thu, 8 Nov 2012, John Peterson wrote:
The error is an unhelpful stack trace ending in an obscure system
function called misaligned_stack_error_entering_dyld_stub_binder().
It typically only shows up in opt mode, so the stack traces aren't
super-helpful anyway.
This is horrifying. I hereby apologize for ever complaining about the
difficulty of debugging C++ template metaprograms.
Speaking of stack traces, can anyone recommend a way to run the
examples in the automake branch through a debugger? I should
probably try
export LIBMESH_OPTIONS=-on_error_attach_debugger
This has actually never worked for me (behavior remains as if the
option was unspecified), yet it's never been a big enough deal (since
-start_in_debugger always worked) for me to want to dig into. But now
that the question's come up, I'm curious about whether the problem is
just me, or whether other libMesh users have the same issue. Between
PETSc error handlers and MPI handlers and Unix signal handlers and
libMesh terminate handlers and application-specific handlers I'm not
surprised if something isn't executing as planned...
---
Roy
------------------------------------------------------------------------------
Everyone hates slow websites. So do we.
Make your web apps faster with AppDynamics
Download AppDynamics Lite for free today:
http://p.sf.net/sfu/appdyn_d2d_nov
_______________________________________________
Libmesh-devel mailing list
Libmesh-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/libmesh-devel
