So it looks like gdb_backtrace() makes a system() call to print the stack
trace info from gdb. Does the system() call not inherit the environment
from that which launched libMesh-based application?
I ask because I've noticed that this will hang if I have a local version of
gdb loaded in my environment, e.g. I've compiled a newer GDB than what's on
my system, made a module, and loaded that module such that it's in the
front of my $PATH. If I don't have that newer gdb version loaded,
everything is fine - the stack trace prints as it's supposed to and all is
well.
So, if I'm understanding the issue correctly, would be there interest in me
adding a --with-gdb configure option that would call a user supplied gdb
version?
My motivation is that this hang can be really annoying because if it's
hanging during a make check, I have to manually kill the process, ctrl-c is
insufficient.
Thanks,
Paul
------------------------------------------------------------------------------
Dive into the World of Parallel Programming. The Go Parallel Website,
sponsored by Intel and developed in partnership with Slashdot Media, is your
hub for all things parallel software development, from weekly thought
leadership blogs to news, videos, case studies, tutorials and more. Take a
look and join the conversation now. http://goparallel.sourceforge.net/
_______________________________________________
Libmesh-devel mailing list
Libmesh-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/libmesh-devel
