I'm just curious what the developers know about the "print_trace" functions in libMesh. I decided to add that functionality to our applications here at the INL yesterday since we expended the use of libmesh_error greatly to the point where we need more contextual information. Derek and I noted the "MAC OS X" Code section near the bottom of that source file which is permanently disabled. Perhaps with a little background information, I might find some time to work on cleaning this up since I have access to plenty of Macs with both Intel and GNU compilers loaded. For now though the other implementation works on our Mac workstations when compiled in debug mode but doesn't demangle which is OK with the people that might actually look at those errors but if it's close to working then maybe I can assist in getting it the rest of the way there.
Cody ------------------------------------------------------------------------------ _______________________________________________ Libmesh-devel mailing list Libmesh-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/libmesh-devel
