Core files under mpich, p4 device
Many of your questions may have already been answered in earlier discussions or in the FAQ. The search results page will indicate current discussions as well as past list serves, articles, and papers.
Jaco Schieke schieke at cae.wisc.eduMon Oct 22 12:14:03 PDT 2001
- Previous message: using mpich 1.2.2.2 with ifc
- Next message: Core files under mpich, p4 device
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
All, Has anybody been able to produce core files under mpich using the p4 device. I have been able to verify on 2 different clusters that SIGSEGV errors under mpich does not produce a core file. Below are the error msgs, but not core files appeared. I have not tried kernel patches to produce named core files - but would first like to know whether this will solve things. How does one produce these? Jaco Schieke Research Assistant Dept. of Chemical Engineering Univ. of Wisconsin Madison Host 1: Linux 2.2.16-22 #1 Tue Aug 22 16:49:06 EDT 2000 i686 unknown p0_26109: p4_error: interrupt SIGSEGV: 11 bm_list_26110: p4_error: interrupt SIGINT: 2 p0_26109: (4.578240) net_send: could not write to fd=4, errno = 32 Host 2: Linux 2.4.6 #1 Sun Aug 19 12:44:48 CDT 2001 i686 unknown p4_32319: p4_error: interrupt SIGSEGV: 11 p2_3383: p4_error: interrupt SIGSEGV: 11 Broken pipe rm_l_5_7126: p4_error: net_recv read: probable EOF on socket: 1 rm_l_1_3581: (1417.766098) net_recv failed for fd = 6 rm_l_1_3581: p4_error: net_recv read, errno = : 104 Cleaning up rm_l_3_5475: (1417.574178) net_recv failed for fd = 6 rm_l_3_5475: p4_error: net_recv read, errno = : 104
- Previous message: using mpich 1.2.2.2 with ifc
- Next message: Core files under mpich, p4 device
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
More information about the Beowulf mailing list