diff options
| author | Miklos Vajna <vmiklos@suse.cz> | 2013-04-18 12:05:10 +0200 |
|---|---|---|
| committer | Miklos Vajna <vmiklos@suse.cz> | 2013-04-18 12:19:33 +0200 |
| commit | 29b59f2e87d1b00ab6a1f4cc4e960603974992bc (patch) | |
| tree | 4f1ee3ef9b8a35548c9062e7b01cae5deade1788 /solenv/bin | |
| parent | 54d0673ba422d6408d8b2d39493a3a7bb4f56037 (diff) | |
gdb-core-bt: don't talk about core files without a reason.
When exit code is <128, then the test probably just failed, it did not
get a SIGSEGV or similar signal, so it's expected that no core file is
created.
Change-Id: Ie9e3599bd6738c04afacb95000d09f9dd2a5c426
Diffstat (limited to 'solenv/bin')
| -rwxr-xr-x | solenv/bin/gdb-core-bt.sh | 3 |
1 files changed, 2 insertions, 1 deletions
diff --git a/solenv/bin/gdb-core-bt.sh b/solenv/bin/gdb-core-bt.sh index 4cbcf52a54b4..52ed3a3b2533 100755 --- a/solenv/bin/gdb-core-bt.sh +++ b/solenv/bin/gdb-core-bt.sh @@ -30,6 +30,7 @@ EXECUTABLE=${1} COREDIR=${2} +EXITCODE=${3} if test -n "$(which gdb)" then @@ -45,7 +46,7 @@ then rm "$GDBCOMMANDFILE" echo exit 0 - else + elif [ $EXITCODE -ge 128 ]; then echo echo "No core file identified in directory ${COREDIR}" echo "To show backtraces for crashes during test execution," |