#LINUX DEBUG FLEXLM DRIVER#

Of course you should remove these 'rude' statements before shipping your moduleВ ) Recompile and (re-)load the module and trigger the error condition - your log now shows you the last line that was successfully executed before the oops happened. Printk(KERN_ALERT 'DEBUG: PassedВ %sВ %d ',_FUNCTION_,_LINE_)

#LINUX DEBUG FLEXLM DRIVER#

If you want to debug an oops (e.g caused by releasing a resource twice) in your driver and you don't have a clue where the oops happens, simply add this line Please use the %z to avoid annoying compile warnings. ssize_t and size_t are quite common values in the kernel, so However please note: always use %zu, %zd or %zx for printing The supported format strings are quite extensively documented in Most of the conversion specifiers supported by the user-space library routine printf() are also available in the kernel there are some notable additions, including '%pf', which will print the symbol name in place of the numeric pointer value, if available. In order to see the kernel messages, just use theД¬ommand in one of your shells - this one will print out the whole kernel log Usually you would print out some more interesting information like Printk works more or less the same way as printf in userspace, so if you ever debugged your userspace program using printf, you are ready to do the same with your kernel code, e.g.

10 Disabling printk messages at compile time.

7.2 Using CONFIG_DEBUG_LL and printascii() (ARM only).

7.1.2 U-boot example on an OMAP OSK board.

7.1.1 Redboot example on a Freescale ADS board.

7.1 Accessing the printk buffer after a silent hang on boot.5 Internals / Changing the size of the printk buffer.

Linux debug flexlm