我更喜欢简单的称呼。所以我用了一些看起来有点复杂，但很容易使用的东西。我通常只是复制并粘贴下面的代码到我的脚本。代码后面有解释。

#This function is used to cleanly exit any script. It does this displaying a
# given error message, and exiting with an error code.
function error_exit {
    echo
    echo "$@"
    exit 1
}
#Trap the killer signals so that we can exit with a good message.
trap "error_exit 'Received signal SIGHUP'" SIGHUP
trap "error_exit 'Received signal SIGINT'" SIGINT
trap "error_exit 'Received signal SIGTERM'" SIGTERM

#Alias the function so that it will print a message with the following format:
#prog-name(@line#): message
#We have to explicitly allow aliases, we do this because they make calling the
#function much easier (see example).
shopt -s expand_aliases
alias die='error_exit "Error ${0}(@`echo $(( $LINENO - 1 ))`):"'

I usually put a call to the cleanup function in side the error_exit function, but this varies from script to script so I left it out. The traps catch the common terminating signals and make sure everything gets cleaned up. The alias is what does the real magic. I like to check everything for failure. So in general I call programs in an "if !" type statement. By subtracting 1 from the line number the alias will tell me where the failure occurred. It is also dead simple to call, and pretty much idiot proof. Below is an example (just replace /bin/false with whatever you are going to call).

#This is an example useage, it will print out
#Error prog-name (@1): Who knew false is false.
if ! /bin/false ; then
    die "Who knew false is false."
fi

我使用

die() {
        echo $1
        kill $$
}

之前;我想因为某种原因，“退出”对我来说是失败的。不过，上面的默认设置似乎是个好主意。

受本文介绍的思想的启发，我在bash样板项目中开发了一种可读且方便的方法来处理bash脚本中的错误。

通过简单地获取库，你可以得到以下结果(即它会在任何错误时停止执行，就像使用set -e一样，这要感谢ERR上的陷阱和一些bash-fu):

还有一些额外的特性可以帮助处理错误，比如try和catch，或者throw关键字，它们允许您在某个点中断执行以查看回溯。此外，如果终端支持它，它会输出电力线表情符号，为输出的部分颜色以提高可读性，并在代码行上下文中强调导致异常的方法。

缺点是—它不可移植—代码在bash中工作，可能仅>= 4(但我可以想象它可以通过一些努力移植到bash 3)。

为了更好地处理，代码被分离到多个文件中，但我受到了Luca Borrione上面回答的回溯思想的启发。

要阅读更多或查看源代码，请参阅GitHub:

https://github.com/niieani/bash-oo-framework#error-handling-with-exceptions-and-throw

我使用以下陷阱代码，它还允许通过管道和“时间”命令跟踪错误

#!/bin/bash
set -o pipefail  # trace ERR through pipes
set -o errtrace  # trace ERR through 'time command' and other functions
function error() {
    JOB="$0"              # job name
    LASTLINE="$1"         # line of error occurrence
    LASTERR="$2"          # error code
    echo "ERROR in ${JOB} : line ${LASTLINE} with exit code ${LASTERR}"
    exit 1
}
trap 'error ${LINENO} ${?}' ERR

这是一个很好的解决方案。我只是想补充一点

set -e

作为一个基本的错误机制。如果一个简单的命令失败，它将立即停止脚本。我认为这应该是默认的行为:因为这样的错误几乎总是意味着一些意想不到的事情，所以继续执行下面的命令是不明智的。

“set -e”的等效替代是

set -o errexit

它使标志的含义比“-e”更清晰。

随机添加:暂时禁用标志，并返回默认值(继续执行，不管退出码)，只需使用

set +e
echo "commands run here returning non-zero exit codes will not cause the entire script to fail"
echo "false returns 1 as an exit code"
false
set -e

这排除了其他响应中提到的正确错误处理，但它是快速有效的(就像bash一样)。