On Fri, Feb 1, 2013 at 9:17 AM, Paul T. Bauman <ptbau...@gmail.com> wrote:
> I agree and have learned to take the bad with the good. Sorry to be a
> broken record, but just in case you missed earlier in the thread, you,
> personally, shouldn't need to mess with the environment, just do
>
> libtool --mode=execute valgrind /path/to/example
>
Cool, I see this even works with typical crud like this
run='./example -some -arguments';
libtool --mode=execute mpiexec -n 1 urxvt -e gdb -ex 'b
SomewhereInteresting' -ex r --args $run : -n 2 $run : -n 1 urxvt -e gdb -ex
'b SomewhereElse' -ex r --args $run
It still needs minor hackery if the executable uses argv[0] or looks for
other resources (e.g., plugins) using a relative path, but those things can
be worked around.
Gmail can be really sucky about picking the correct address for a reply;
sorry about that. (It does it right for most lists, but I don't know why
that delivery information isn't in the libmesh-devel headers.)
------------------------------------------------------------------------------
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_jan
_______________________________________________
Libmesh-devel mailing list
Libmesh-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/libmesh-devel
