On Nov 8, 2012, at 10:21 AM, John Peterson <jwpeter...@gmail.com> wrote: > > It typically only shows up in opt mode, so the stack traces aren't > super-helpful anyway. > > 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 > > and see if that works.
>From libtool, uninstalled 'executables' are really libtool shell scripts that >handle setting library paths properly. This is weird but I believe they have >their reasons. So you can actually 'less' the example and see what I'm talking about… But to launch it in the debugger, do $ libtool --mode=executde gdb ./introduction-ex1 for example. (Yes, I plan to update the site documentation to contain this sort of thing before merging this.) > Definitely try opt mode, that's where I see the segfaults, for example in > adjoints_ex1. No special LIBMESH_RUN or LIBMESH_OPTIONS, just hand-built > compilers and no macports. Not sure if it was mentioned, but macports is not > really an option for us since for some reason our site blocks rsync :-P No, you should have mentioned earlier! ;-) Mine does too - but you can set up macports to work from an svn checkout instead of rsync, which is what I do. https://trac.macports.org/wiki/howto/SyncingWithSVN My only gripe here is you need to be somewhat careful what revision you are at, because trunk is not always stable. So watch for the rREVS that correspond to releases. -Ben ------------------------------------------------------------------------------ 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
