From: Bartosz Golaszewski <bgolaszewski@baylibre.com>
To: LKML <linux-kernel@vger.kernel.org>
Cc: linux-kbuild <linux-kbuild@vger.kernel.org>,
Bartosz Golaszewski <bgolaszewski@baylibre.com>
Subject: [RFC] scripts: kerrno.sh - errno translator
Date: Thu, 30 Apr 2015 12:53:35 +0200 [thread overview]
Message-ID: <1430391215-13768-1-git-send-email-bgolaszewski@baylibre.com> (raw)
Shell script allowing to find errno definitions and descriptions in the
kernel source.
Signed-off-by: Bartosz Golaszewski <bgolaszewski@baylibre.com>
---
This is a simple script I use when seeing messages like:
some_func() failed: -123
to find out the actual errno meaning. The usage is very simple - just
call 'scripts/kerrno.sh 1 4 -50 (...)'.
I'm sending this as RFC in order to find out if there's any interest in merging
this script with the kernel code.
scripts/kerrno.sh | 62 +++++++++++++++++++++++++++++++++++++++++++++++++++++++
1 file changed, 62 insertions(+)
create mode 100755 scripts/kerrno.sh
diff --git a/scripts/kerrno.sh b/scripts/kerrno.sh
new file mode 100755
index 0000000..ebdc8da
--- /dev/null
+++ b/scripts/kerrno.sh
@@ -0,0 +1,62 @@
+#!/bin/sh
+
+# Get preprocessor definitions and descriptions of errno numbers from the
+# Linux kernel source.
+#
+# This script parses all the C headers containing errno definitions in the
+# Linux source tree and extracts their definitions and corresponding
+# descriptions in order to quickly give users an idea on what kind of
+# an error they're dealing with.
+#
+# Example:
+# scripts/kerrno.sh 43 -12 3
+#
+# Should be called from the top of the source tree.
+#
+# Copyright (C) 2015 Bartosz Golaszewski <bgolaszewski@baylibre.com>
+
+FILEPTRN=".*errno.*\.[ch]$"
+ERRNOPTRN="\#define[\ \t]+E[A-Z0-9]+[\ \t]+[0-9]+[\ \t]+"
+
+usage()
+{
+ echo "$0: get info for error numbers"
+ echo
+ echo "Usage:"
+ echo "\t$0 <errno numbers>"
+ echo
+ echo "\tExample: $0 -18 34 128"
+ echo
+}
+
+if [ "$#" -eq "0" ] || ([ "$#" -eq "1" ] && [ "$1" = "--help" ])
+then
+ usage
+ exit
+fi
+
+for WANTED in $@
+do
+ case ${WANTED#-} in
+ ''|*[!0-9]*)
+ echo "$WANTED: not a number";
+ continue;
+ ;;
+ esac
+
+ test "$WANTED" -lt "0" && WANTED=$(echo -n $WANTED | cut -d'-' -f2)
+
+ echo "Errno $WANTED:"
+ find ./ -regex "$FILEPTRN" -exec grep -nPH "$ERRNOPTRN" {} \; \
+ | tr -s ':' ' ' \
+ | tr -s '\t' ' ' \
+ | cut -d' ' -f1,2,4,5 | while read FILE LINE ERRNO NUM
+ do
+ if [ "$NUM" -eq "$WANTED" ]
+ then
+ echo -n "\t$ERRNO ("
+ echo -n "$(head $FILE -n $LINE | tail -1 | cut -d'*' -f2)"
+ echo ") defined in $FILE:$LINE"
+ fi
+ done
+done
--
2.1.4
next reply other threads:[~2015-04-30 10:53 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-30 10:53 Bartosz Golaszewski [this message]
2015-04-30 11:04 ` Richard Weinberger
2015-04-30 11:29 ` Bartosz Golaszewski
2015-04-30 12:25 ` David Sterba
2015-04-30 12:33 ` Richard Weinberger
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1430391215-13768-1-git-send-email-bgolaszewski@baylibre.com \
--to=bgolaszewski@baylibre.com \
--cc=linux-kbuild@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®