ports/openmpi
ports/openmpi
1
1
Форкнуть 0
Код Релизы Активность
f2e33c725f
openmpi/ompi/errhandler/help-mpi-errors.txt

41 строка
1.5 KiB
Plaintext
Исходник Обычный вид История

Enable aggregation checking for "*** An error occurred..." MPI layer help messages so that users only see the message once instead of N times when their MPI app crashes. Note that there is a tradeoff here -- we now call malloc in this particular "show the error" code path. This shouldn't usually be a problem, because the errors typically displayed through this mechanism are MPI API argument problems (e.g., sending a negative count to MPI_SEND), and not memory errors. But such API argument errors could be a consequence of of a prior memory error, so there's a nonzero chance that the error failure will fail to print because malloc failed. In this case, the user can disable help message aggregation (via the orte_base_want_aggregate MCA parameter) and we'll fall back to the no-malloc code path (but without aggregation). Note that we won't aggregate before MPI_INIT or after MPI_FINALIZE. So if you call an MPI function before MPI_INIT / after MPI_FINALIZE, you'll still see the error message N times. Nothing we can do about that; we need ORTE to do the aggregation properly (which is obviously unavailable before MPI_INIT / after MPI_FINALIZE). This commit was SVN r19611.
2008-09-23 21:19:24 +04:00
# -*- text -*-
#
# Copyright (c) 2004-2005 The Trustees of Indiana University and Indiana
# 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.
Purge whitespace from the repo
2015-06-24 06:59:57 +03:00
# Copyright (c) 2004-2005 High Performance Computing Center Stuttgart,
Enable aggregation checking for "*** An error occurred..." MPI layer help messages so that users only see the message once instead of N times when their MPI app crashes. Note that there is a tradeoff here -- we now call malloc in this particular "show the error" code path. This shouldn't usually be a problem, because the errors typically displayed through this mechanism are MPI API argument problems (e.g., sending a negative count to MPI_SEND), and not memory errors. But such API argument errors could be a consequence of of a prior memory error, so there's a nonzero chance that the error failure will fail to print because malloc failed. In this case, the user can disable help message aggregation (via the orte_base_want_aggregate MCA parameter) and we'll fall back to the no-malloc code path (but without aggregation). Note that we won't aggregate before MPI_INIT or after MPI_FINALIZE. So if you call an MPI function before MPI_INIT / after MPI_FINALIZE, you'll still see the error message N times. Nothing we can do about that; we need ORTE to do the aggregation properly (which is obviously unavailable before MPI_INIT / after MPI_FINALIZE). This commit was SVN r19611.
2008-09-23 21:19:24 +04:00
# University of Stuttgart. All rights reserved.
# Copyright (c) 2004-2005 The Regents of the University of California.
# All rights reserved.
Fix a few issues with error messages: * If something goes wrong during ompi_mpi_init, don't erroneously report that it is illegal to invoke MPI_INIT* before MPI_INIT * Aggregate help messages when possible when something goes wring during ompi_mpi_init This commit was SVN r24492.
2011-03-07 19:45:45 +03:00
# Copyright (c) 2008-2011 Cisco Systems, Inc. All rights reserved.
Fix missing functionality in MPI_Abort so that the group of peers defined by the communicator that should be aborted with this process are requested from the runtime before the local process exits. Per RFC: http://www.open-mpi.org/community/lists/devel/2011/06/9335.php This commit was SVN r24775.
2011-06-15 17:10:13 +04:00
# Copyright (c) 2010-2011 Oak Ridge National Labs. All rights reserved.
Enable aggregation checking for "*** An error occurred..." MPI layer help messages so that users only see the message once instead of N times when their MPI app crashes. Note that there is a tradeoff here -- we now call malloc in this particular "show the error" code path. This shouldn't usually be a problem, because the errors typically displayed through this mechanism are MPI API argument problems (e.g., sending a negative count to MPI_SEND), and not memory errors. But such API argument errors could be a consequence of of a prior memory error, so there's a nonzero chance that the error failure will fail to print because malloc failed. In this case, the user can disable help message aggregation (via the orte_base_want_aggregate MCA parameter) and we'll fall back to the no-malloc code path (but without aggregation). Note that we won't aggregate before MPI_INIT or after MPI_FINALIZE. So if you call an MPI function before MPI_INIT / after MPI_FINALIZE, you'll still see the error message N times. Nothing we can do about that; we need ORTE to do the aggregation properly (which is obviously unavailable before MPI_INIT / after MPI_FINALIZE). This commit was SVN r19611.
2008-09-23 21:19:24 +04:00
# $COPYRIGHT$
Purge whitespace from the repo
2015-06-24 06:59:57 +03:00
#
Enable aggregation checking for "*** An error occurred..." MPI layer help messages so that users only see the message once instead of N times when their MPI app crashes. Note that there is a tradeoff here -- we now call malloc in this particular "show the error" code path. This shouldn't usually be a problem, because the errors typically displayed through this mechanism are MPI API argument problems (e.g., sending a negative count to MPI_SEND), and not memory errors. But such API argument errors could be a consequence of of a prior memory error, so there's a nonzero chance that the error failure will fail to print because malloc failed. In this case, the user can disable help message aggregation (via the orte_base_want_aggregate MCA parameter) and we'll fall back to the no-malloc code path (but without aggregation). Note that we won't aggregate before MPI_INIT or after MPI_FINALIZE. So if you call an MPI function before MPI_INIT / after MPI_FINALIZE, you'll still see the error message N times. Nothing we can do about that; we need ORTE to do the aggregation properly (which is obviously unavailable before MPI_INIT / after MPI_FINALIZE). This commit was SVN r19611.
2008-09-23 21:19:24 +04:00
# Additional copyrights may follow
Purge whitespace from the repo
2015-06-24 06:59:57 +03:00
#
Enable aggregation checking for "*** An error occurred..." MPI layer help messages so that users only see the message once instead of N times when their MPI app crashes. Note that there is a tradeoff here -- we now call malloc in this particular "show the error" code path. This shouldn't usually be a problem, because the errors typically displayed through this mechanism are MPI API argument problems (e.g., sending a negative count to MPI_SEND), and not memory errors. But such API argument errors could be a consequence of of a prior memory error, so there's a nonzero chance that the error failure will fail to print because malloc failed. In this case, the user can disable help message aggregation (via the orte_base_want_aggregate MCA parameter) and we'll fall back to the no-malloc code path (but without aggregation). Note that we won't aggregate before MPI_INIT or after MPI_FINALIZE. So if you call an MPI function before MPI_INIT / after MPI_FINALIZE, you'll still see the error message N times. Nothing we can do about that; we need ORTE to do the aggregation properly (which is obviously unavailable before MPI_INIT / after MPI_FINALIZE). This commit was SVN r19611.
2008-09-23 21:19:24 +04:00
# $HEADER$
#
# *** THESE MESSAGES ARE COORDINATED WITH FIXED STRINGS IN
# *** errhandler_predefined.c! Do not change these messages without also
# *** changing errhandler_predefined.c!
#
[mpi_errors_are_fatal]
%s *** An error occurred %s %s
Fix missing functionality in MPI_Abort so that the group of peers defined by the communicator that should be aborted with this process are requested from the runtime before the local process exits. Per RFC: http://www.open-mpi.org/community/lists/devel/2011/06/9335.php This commit was SVN r24775.
2011-06-15 17:10:13 +04:00
%s *** reported by process [%lu,%lu]
Enable aggregation checking for "*** An error occurred..." MPI layer help messages so that users only see the message once instead of N times when their MPI app crashes. Note that there is a tradeoff here -- we now call malloc in this particular "show the error" code path. This shouldn't usually be a problem, because the errors typically displayed through this mechanism are MPI API argument problems (e.g., sending a negative count to MPI_SEND), and not memory errors. But such API argument errors could be a consequence of of a prior memory error, so there's a nonzero chance that the error failure will fail to print because malloc failed. In this case, the user can disable help message aggregation (via the orte_base_want_aggregate MCA parameter) and we'll fall back to the no-malloc code path (but without aggregation). Note that we won't aggregate before MPI_INIT or after MPI_FINALIZE. So if you call an MPI function before MPI_INIT / after MPI_FINALIZE, you'll still see the error message N times. Nothing we can do about that; we need ORTE to do the aggregation properly (which is obviously unavailable before MPI_INIT / after MPI_FINALIZE). This commit was SVN r19611.
2008-09-23 21:19:24 +04:00
%s *** on %s %s
%s *** %s
Fix missing functionality in MPI_Abort so that the group of peers defined by the communicator that should be aborted with this process are requested from the runtime before the local process exits. Per RFC: http://www.open-mpi.org/community/lists/devel/2011/06/9335.php This commit was SVN r24775.
2011-06-15 17:10:13 +04:00
%s *** MPI_ERRORS_ARE_FATAL (processes in this %s will now abort,
%s *** and potentially your MPI job)
Enable aggregation checking for "*** An error occurred..." MPI layer help messages so that users only see the message once instead of N times when their MPI app crashes. Note that there is a tradeoff here -- we now call malloc in this particular "show the error" code path. This shouldn't usually be a problem, because the errors typically displayed through this mechanism are MPI API argument problems (e.g., sending a negative count to MPI_SEND), and not memory errors. But such API argument errors could be a consequence of of a prior memory error, so there's a nonzero chance that the error failure will fail to print because malloc failed. In this case, the user can disable help message aggregation (via the orte_base_want_aggregate MCA parameter) and we'll fall back to the no-malloc code path (but without aggregation). Note that we won't aggregate before MPI_INIT or after MPI_FINALIZE. So if you call an MPI function before MPI_INIT / after MPI_FINALIZE, you'll still see the error message N times. Nothing we can do about that; we need ORTE to do the aggregation properly (which is obviously unavailable before MPI_INIT / after MPI_FINALIZE). This commit was SVN r19611.
2008-09-23 21:19:24 +04:00
#
[mpi_errors_are_fatal unknown handle]
%s *** An error occurred %s %s
Fix missing functionality in MPI_Abort so that the group of peers defined by the communicator that should be aborted with this process are requested from the runtime before the local process exits. Per RFC: http://www.open-mpi.org/community/lists/devel/2011/06/9335.php This commit was SVN r24775.
2011-06-15 17:10:13 +04:00
%s *** reported by process [%lu,%lu]
Enable aggregation checking for "*** An error occurred..." MPI layer help messages so that users only see the message once instead of N times when their MPI app crashes. Note that there is a tradeoff here -- we now call malloc in this particular "show the error" code path. This shouldn't usually be a problem, because the errors typically displayed through this mechanism are MPI API argument problems (e.g., sending a negative count to MPI_SEND), and not memory errors. But such API argument errors could be a consequence of of a prior memory error, so there's a nonzero chance that the error failure will fail to print because malloc failed. In this case, the user can disable help message aggregation (via the orte_base_want_aggregate MCA parameter) and we'll fall back to the no-malloc code path (but without aggregation). Note that we won't aggregate before MPI_INIT or after MPI_FINALIZE. So if you call an MPI function before MPI_INIT / after MPI_FINALIZE, you'll still see the error message N times. Nothing we can do about that; we need ORTE to do the aggregation properly (which is obviously unavailable before MPI_INIT / after MPI_FINALIZE). This commit was SVN r19611.
2008-09-23 21:19:24 +04:00
%s *** on a NULL %s
%s *** %s
Fix missing functionality in MPI_Abort so that the group of peers defined by the communicator that should be aborted with this process are requested from the runtime before the local process exits. Per RFC: http://www.open-mpi.org/community/lists/devel/2011/06/9335.php This commit was SVN r24775.
2011-06-15 17:10:13 +04:00
%s *** MPI_ERRORS_ARE_FATAL (processes in this %s will now abort,
%s *** and potentially your MPI job)
Enable aggregation checking for "*** An error occurred..." MPI layer help messages so that users only see the message once instead of N times when their MPI app crashes. Note that there is a tradeoff here -- we now call malloc in this particular "show the error" code path. This shouldn't usually be a problem, because the errors typically displayed through this mechanism are MPI API argument problems (e.g., sending a negative count to MPI_SEND), and not memory errors. But such API argument errors could be a consequence of of a prior memory error, so there's a nonzero chance that the error failure will fail to print because malloc failed. In this case, the user can disable help message aggregation (via the orte_base_want_aggregate MCA parameter) and we'll fall back to the no-malloc code path (but without aggregation). Note that we won't aggregate before MPI_INIT or after MPI_FINALIZE. So if you call an MPI function before MPI_INIT / after MPI_FINALIZE, you'll still see the error message N times. Nothing we can do about that; we need ORTE to do the aggregation properly (which is obviously unavailable before MPI_INIT / after MPI_FINALIZE). This commit was SVN r19611.
2008-09-23 21:19:24 +04:00
#
Копировать постоянную ссылку