ports/openmpi
ports/openmpi
1
1
Форкнуть 0
Код Релизы Активность
9d7cb82bba
openmpi/opal/util/stacktrace.h

43 строки
1.2 KiB
C
Исходник Обычный вид История

Add a Stacktrace feature, which figures where/what signal has happened after MPI-startup. For this a new mpirun-parameter "mpi_signal" is added, one may specify a comma-separated list of signals to grab, e.g. mpirun --mca mpi_signal 8,11 will check for SIGFPE and SIGSEGV. It only finds the first fault (SA_ONESHOT), as after the return the same fault will occur again. As printout, the data provided by siginfo_t is printed to STDOUT (yes, it calls printf ,-]). Additionally, with glibc, it uses backtrace and backtrace_symbols to print the calling stack up to the function in which the signal was raised: (Rank:0) Going to write to RD_ONLY mmaped shared mem Signal:11 info.si_errno:0(Success) si_code:2(SEGV_ACCERR) Failing at addr:0x4020c000 [0] func:/home/rusraink/ompi-gcc/lib/libmpi.so.0 [0x40121afe] [1] func:./t0 [0x42029180] [2] func:./t0(__libc_start_main+0x95) [0x42017589] [3] func:./t0(__libc_start_main+0x49) [0x8048691] This commit was SVN r4170.
2005-01-26 22:11:46 +03:00
/*
Change a bunch of 'OMPI' names to OPAL names, since this is opal. This commit was SVN r14165.
2007-03-29 05:00:33 +04:00
* Copyright (c) 2004-2007 The Trustees of Indiana University and Indiana
Update the copyright notices for IU and UTK. This commit was SVN r7999.
2005-11-05 22:57:48 +03:00
* University Research and Technology
* Corporation. All rights reserved.
* Copyright (c) 2004-2005 The University of Tennessee and The University
* of Tennessee Research Foundation. All rights
* reserved.
Add a Stacktrace feature, which figures where/what signal has happened after MPI-startup. For this a new mpirun-parameter "mpi_signal" is added, one may specify a comma-separated list of signals to grab, e.g. mpirun --mca mpi_signal 8,11 will check for SIGFPE and SIGSEGV. It only finds the first fault (SA_ONESHOT), as after the return the same fault will occur again. As printout, the data provided by siginfo_t is printed to STDOUT (yes, it calls printf ,-]). Additionally, with glibc, it uses backtrace and backtrace_symbols to print the calling stack up to the function in which the signal was raised: (Rank:0) Going to write to RD_ONLY mmaped shared mem Signal:11 info.si_errno:0(Success) si_code:2(SEGV_ACCERR) Failing at addr:0x4020c000 [0] func:/home/rusraink/ompi-gcc/lib/libmpi.so.0 [0x40121afe] [1] func:./t0 [0x42029180] [2] func:./t0(__libc_start_main+0x95) [0x42017589] [3] func:./t0(__libc_start_main+0x49) [0x8048691] This commit was SVN r4170.
2005-01-26 22:11:46 +03:00
* Copyright (c) 2004-2005 High Performance Computing Center Stuttgart,
* University of Stuttgart. All rights reserved.
Add UC copyright This commit was SVN r5009.
2005-03-24 15:43:37 +03:00
* Copyright (c) 2004-2005 The Regents of the University of California.
* All rights reserved.
Add a Stacktrace feature, which figures where/what signal has happened after MPI-startup. For this a new mpirun-parameter "mpi_signal" is added, one may specify a comma-separated list of signals to grab, e.g. mpirun --mca mpi_signal 8,11 will check for SIGFPE and SIGSEGV. It only finds the first fault (SA_ONESHOT), as after the return the same fault will occur again. As printout, the data provided by siginfo_t is printed to STDOUT (yes, it calls printf ,-]). Additionally, with glibc, it uses backtrace and backtrace_symbols to print the calling stack up to the function in which the signal was raised: (Rank:0) Going to write to RD_ONLY mmaped shared mem Signal:11 info.si_errno:0(Success) si_code:2(SEGV_ACCERR) Failing at addr:0x4020c000 [0] func:/home/rusraink/ompi-gcc/lib/libmpi.so.0 [0x40121afe] [1] func:./t0 [0x42029180] [2] func:./t0(__libc_start_main+0x95) [0x42017589] [3] func:./t0(__libc_start_main+0x49) [0x8048691] This commit was SVN r4170.
2005-01-26 22:11:46 +03:00
* $COPYRIGHT$
*
* Additional copyrights may follow
*
* $HEADER$
Always flush to get a slightly better guarantee of getting the error message out. Use stderr, and put a "yes, we're done with the error message" marker at the end of the error message so that you know if you saw it all or the message was truncated. This commit was SVN r4333.
2005-02-09 06:08:13 +03:00
*
* @file
Add a Stacktrace feature, which figures where/what signal has happened after MPI-startup. For this a new mpirun-parameter "mpi_signal" is added, one may specify a comma-separated list of signals to grab, e.g. mpirun --mca mpi_signal 8,11 will check for SIGFPE and SIGSEGV. It only finds the first fault (SA_ONESHOT), as after the return the same fault will occur again. As printout, the data provided by siginfo_t is printed to STDOUT (yes, it calls printf ,-]). Additionally, with glibc, it uses backtrace and backtrace_symbols to print the calling stack up to the function in which the signal was raised: (Rank:0) Going to write to RD_ONLY mmaped shared mem Signal:11 info.si_errno:0(Success) si_code:2(SEGV_ACCERR) Failing at addr:0x4020c000 [0] func:/home/rusraink/ompi-gcc/lib/libmpi.so.0 [0x40121afe] [1] func:./t0 [0x42029180] [2] func:./t0(__libc_start_main+0x95) [0x42017589] [3] func:./t0(__libc_start_main+0x49) [0x8048691] This commit was SVN r4170.
2005-01-26 22:11:46 +03:00
*/
Change a bunch of 'OMPI' names to OPAL names, since this is opal. This commit was SVN r14165.
2007-03-29 05:00:33 +04:00
#ifndef OPAL_STACKTRACE_H
#define OPAL_STACKTRACE_H
Add a Stacktrace feature, which figures where/what signal has happened after MPI-startup. For this a new mpirun-parameter "mpi_signal" is added, one may specify a comma-separated list of signals to grab, e.g. mpirun --mca mpi_signal 8,11 will check for SIGFPE and SIGSEGV. It only finds the first fault (SA_ONESHOT), as after the return the same fault will occur again. As printout, the data provided by siginfo_t is printed to STDOUT (yes, it calls printf ,-]). Additionally, with glibc, it uses backtrace and backtrace_symbols to print the calling stack up to the function in which the signal was raised: (Rank:0) Going to write to RD_ONLY mmaped shared mem Signal:11 info.si_errno:0(Success) si_code:2(SEGV_ACCERR) Failing at addr:0x4020c000 [0] func:/home/rusraink/ompi-gcc/lib/libmpi.so.0 [0x40121afe] [1] func:./t0 [0x42029180] [2] func:./t0(__libc_start_main+0x95) [0x42017589] [3] func:./t0(__libc_start_main+0x49) [0x8048691] This commit was SVN r4170.
2005-01-26 22:11:46 +03:00
Next step in the project split, mainly source code re-arranging - move files out of toplevel include/ and etc/, moving it into the sub-projects - rather than including config headers with <project>/include, have them as <project> - require all headers to be included with a project prefix, with the exception of the config headers ({opal,orte,ompi}_config.h mpi.h, and mpif.h) This commit was SVN r8985.
2006-02-12 04:33:29 +03:00
#include "opal_config.h"
Add a Stacktrace feature, which figures where/what signal has happened after MPI-startup. For this a new mpirun-parameter "mpi_signal" is added, one may specify a comma-separated list of signals to grab, e.g. mpirun --mca mpi_signal 8,11 will check for SIGFPE and SIGSEGV. It only finds the first fault (SA_ONESHOT), as after the return the same fault will occur again. As printout, the data provided by siginfo_t is printed to STDOUT (yes, it calls printf ,-]). Additionally, with glibc, it uses backtrace and backtrace_symbols to print the calling stack up to the function in which the signal was raised: (Rank:0) Going to write to RD_ONLY mmaped shared mem Signal:11 info.si_errno:0(Success) si_code:2(SEGV_ACCERR) Failing at addr:0x4020c000 [0] func:/home/rusraink/ompi-gcc/lib/libmpi.so.0 [0x40121afe] [1] func:./t0 [0x42029180] [2] func:./t0(__libc_start_main+0x95) [0x42017589] [3] func:./t0(__libc_start_main+0x49) [0x8048691] This commit was SVN r4170.
2005-01-26 22:11:46 +03:00
#ifdef HAVE_SIGNAL_H
#include <signal.h>
#endif
* results from initial merge of the tim branch into the trunk. Compiles and ompi_info works, but that's all that has been tested. This commit was SVN r4827.
2005-03-14 23:57:21 +03:00
Add a Stacktrace feature, which figures where/what signal has happened after MPI-startup. For this a new mpirun-parameter "mpi_signal" is added, one may specify a comma-separated list of signals to grab, e.g. mpirun --mca mpi_signal 8,11 will check for SIGFPE and SIGSEGV. It only finds the first fault (SA_ONESHOT), as after the return the same fault will occur again. As printout, the data provided by siginfo_t is printed to STDOUT (yes, it calls printf ,-]). Additionally, with glibc, it uses backtrace and backtrace_symbols to print the calling stack up to the function in which the signal was raised: (Rank:0) Going to write to RD_ONLY mmaped shared mem Signal:11 info.si_errno:0(Success) si_code:2(SEGV_ACCERR) Failing at addr:0x4020c000 [0] func:/home/rusraink/ompi-gcc/lib/libmpi.so.0 [0x40121afe] [1] func:./t0 [0x42029180] [2] func:./t0(__libc_start_main+0x95) [0x42017589] [3] func:./t0(__libc_start_main+0x49) [0x8048691] This commit was SVN r4170.
2005-01-26 22:11:46 +03:00
/**
* rename ompi_show_help to opal_show_help * rename ompi_stacktrace to opal_stacktrace * rename ompi_strncpy to opal_strncpy This commit was SVN r6336.
2005-07-04 06:38:44 +04:00
* Here we register the opal_show_stackframe function for signals
Add a Stacktrace feature, which figures where/what signal has happened after MPI-startup. For this a new mpirun-parameter "mpi_signal" is added, one may specify a comma-separated list of signals to grab, e.g. mpirun --mca mpi_signal 8,11 will check for SIGFPE and SIGSEGV. It only finds the first fault (SA_ONESHOT), as after the return the same fault will occur again. As printout, the data provided by siginfo_t is printed to STDOUT (yes, it calls printf ,-]). Additionally, with glibc, it uses backtrace and backtrace_symbols to print the calling stack up to the function in which the signal was raised: (Rank:0) Going to write to RD_ONLY mmaped shared mem Signal:11 info.si_errno:0(Success) si_code:2(SEGV_ACCERR) Failing at addr:0x4020c000 [0] func:/home/rusraink/ompi-gcc/lib/libmpi.so.0 [0x40121afe] [1] func:./t0 [0x42029180] [2] func:./t0(__libc_start_main+0x95) [0x42017589] [3] func:./t0(__libc_start_main+0x49) [0x8048691] This commit was SVN r4170.
2005-01-26 22:11:46 +03:00
* passed to OpenMPI by the mpi_signal-parameter passed to mpirun
* by the user.
*
Next step in the project split, mainly source code re-arranging - move files out of toplevel include/ and etc/, moving it into the sub-projects - rather than including config headers with <project>/include, have them as <project> - require all headers to be included with a project prefix, with the exception of the config headers ({opal,orte,ompi}_config.h mpi.h, and mpif.h) This commit was SVN r8985.
2006-02-12 04:33:29 +03:00
* @returnvalue OPAL_SUCCESS
* @returnvalue OPAL_ERR_BAD_PARAM if the value in the signal-list
Add a Stacktrace feature, which figures where/what signal has happened after MPI-startup. For this a new mpirun-parameter "mpi_signal" is added, one may specify a comma-separated list of signals to grab, e.g. mpirun --mca mpi_signal 8,11 will check for SIGFPE and SIGSEGV. It only finds the first fault (SA_ONESHOT), as after the return the same fault will occur again. As printout, the data provided by siginfo_t is printed to STDOUT (yes, it calls printf ,-]). Additionally, with glibc, it uses backtrace and backtrace_symbols to print the calling stack up to the function in which the signal was raised: (Rank:0) Going to write to RD_ONLY mmaped shared mem Signal:11 info.si_errno:0(Success) si_code:2(SEGV_ACCERR) Failing at addr:0x4020c000 [0] func:/home/rusraink/ompi-gcc/lib/libmpi.so.0 [0x40121afe] [1] func:./t0 [0x42029180] [2] func:./t0(__libc_start_main+0x95) [0x42017589] [3] func:./t0(__libc_start_main+0x49) [0x8048691] This commit was SVN r4170.
2005-01-26 22:11:46 +03:00
* is not a valid signal-number
*
*/
Windows friendly version. We have to split the OMPI_DECLSPEC in at least 3 different macros, one for each project. Therefore, now we have OPAL_DECLSPEC, ORTE_DECLSPEC and OMPI_DECLSPEC. Please use them based on the sub-project. This commit was SVN r11270.
2006-08-20 19:54:04 +04:00
OPAL_DECLSPEC int opal_util_register_stackhandlers (void);
Add a Stacktrace feature, which figures where/what signal has happened after MPI-startup. For this a new mpirun-parameter "mpi_signal" is added, one may specify a comma-separated list of signals to grab, e.g. mpirun --mca mpi_signal 8,11 will check for SIGFPE and SIGSEGV. It only finds the first fault (SA_ONESHOT), as after the return the same fault will occur again. As printout, the data provided by siginfo_t is printed to STDOUT (yes, it calls printf ,-]). Additionally, with glibc, it uses backtrace and backtrace_symbols to print the calling stack up to the function in which the signal was raised: (Rank:0) Going to write to RD_ONLY mmaped shared mem Signal:11 info.si_errno:0(Success) si_code:2(SEGV_ACCERR) Failing at addr:0x4020c000 [0] func:/home/rusraink/ompi-gcc/lib/libmpi.so.0 [0x40121afe] [1] func:./t0 [0x42029180] [2] func:./t0(__libc_start_main+0x95) [0x42017589] [3] func:./t0(__libc_start_main+0x49) [0x8048691] This commit was SVN r4170.
2005-01-26 22:11:46 +03:00
Change a bunch of 'OMPI' names to OPAL names, since this is opal. This commit was SVN r14165.
2007-03-29 05:00:33 +04:00
#endif /* OPAL_STACKTRACE_H */
Копировать постоянную ссылку