4e33e6aeaa
The OPAL SOS framework tries to meet the following objectives: * reduce the cascading error messages and the amount of code needed to print an error message. * build and aggregate stacks of encountered errors and associate related individual errors with each other. * allow registration of custom callbacks to intercept error events. For more information, refer to https://svn.open-mpi.org/trac/ompi/wiki/ErrorMessages This commit was SVN r23158.
37 строки
1.1 KiB
Plaintext
37 строки
1.1 KiB
Plaintext
# -*- 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.
|
|
# Copyright (c) 2004-2005 High Performance Computing Center Stuttgart,
|
|
# University of Stuttgart. All rights reserved.
|
|
# Copyright (c) 2004-2005 The Regents of the University of California.
|
|
# All rights reserved.
|
|
# Copyright (c) 2008 Cisco Systems, Inc. All rights reserved.
|
|
# $COPYRIGHT$
|
|
#
|
|
# Additional copyrights may follow
|
|
#
|
|
# $HEADER$
|
|
#
|
|
# This is the US/English help file for OPAL SOS error messages.
|
|
#
|
|
# FORMAT:
|
|
# <severity> filename:linenum:functionname
|
|
# error message string
|
|
# stacktrace (optional)
|
|
[general message]
|
|
| |--<%s> at %s:%d:%s():
|
|
| | %s
|
|
#
|
|
[msg header]
|
|
| %s
|
|
#
|
|
# We marshall all the parameters into a single message when we
|
|
# relay it to the notifier.
|
|
[notifier message]
|
|
%s
|