I'm taking another look at making our assert()/error()/abort()/throw() behavior more consistent and more useful, but with the levels of code below us it's not easy. If one process fails an assert(), for instance, it eventually dies with an abort() and returns an error code to the OS, but for some reason the other processes give errors like this to stderr:
p1_22444: p4_error: interrupt SIGx: 6 rm_l_1_22503: (180.959010) net_send: could not write to fd=5, errno = 32 And non-errors like this to the shell: prandtl (82)$ echo $? 0 Any idea where those p4_error and net_send messages are coming from and how I can intercept them? (Signal handlers?) In addition to giving accurate return codes to invokers such as make, I'd like to make stack trace dumps and core dumps (from all processors) into an optional feature. --- Roy ------------------------------------------------------------------------- This SF.net email is sponsored by the 2008 JavaOne(SM) Conference Don't miss this year's exciting event. There's still time to save $100. Use priority code J8TL2D2. http://ad.doubleclick.net/clk;198757673;13503038;p?http://java.sun.com/javaone _______________________________________________ Libmesh-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/libmesh-devel
