Am 30.04.2015 um 14:25 schrieb David Sterba: > On Thu, Apr 30, 2015 at 01:29:41PM +0200, Bartosz Golaszewski wrote: >> 2015-04-30 13:04 GMT+02:00 Richard Weinberger <richard.weinberger@xxxxxxxxx>: >>> On Thu, Apr 30, 2015 at 12:53 PM, Bartosz Golaszewski >>> <bgolaszewski@xxxxxxxxxxxx> wrote: >>>> Shell script allowing to find errno definitions and descriptions in the >>>> kernel source. >>>> >>>> Signed-off-by: Bartosz Golaszewski <bgolaszewski@xxxxxxxxxxxx> >>>> --- >>>> This is a simple script I use when seeing messages like: >>>> >>>> some_func() failed: -123 >>> >>> What is wrong with a one-liner like: >>> gcc -E -dD - < include/uapi/linux/errno.h |grep -E "^#define E.* 123$" >> >> Nothing really - the output is less nice, that's all. > > I'd find a helper script useful in situations where I don't know the > error code immediatelly and have to convert it from a hexa value first. > Eg. when RAX contains an error code after a BUG_ON: > > RAX: 00000000ffffffe4 > > this translates to -28 == -ENOSPC. You mean a script where you can pipe a register dump into and it tries to translate all registers values to meaningful values? Yes, that would be nice... :) Thanks, //richard -- To unsubscribe from this list: send the line "unsubscribe linux-kbuild" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
