Message not appearing in mesg

Message not appearing in mesg

[Sébastien Hinderer]

Dear all,

I have a module that uses pr_debug at init.
Although the module is successfully loaded, the message appears
neither in dmesg, nor at the console. I tried toprint a 8 to
/proc/sys/kernel/printk but that does not change anything.

Any hint would be warmly appreciated.

Thanks!

S?bastien.

Message not appearing in mesg

[Luis de Bethencourt]

On 7 July 2015 at 15:53, S?bastien Hinderer <Sebastien.Hinderer@ens-lyon.org
> wrote:

> Dear all,
>
> I have a module that uses pr_debug at init.
> Although the module is successfully loaded, the message appears
> neither in dmesg, nor at the console. I tried toprint a 8 to
> /proc/sys/kernel/printk but that does not change anything.
>
> Any hint would be warmly appreciated.
>
> Thanks!
>
> S?bastien


Do you have the relevant DEBUG macros activated in your kernel's
configuration?
https://www.kernel.org/doc/local/pr_debug.txt
http://elinux.org/Debugging_by_printing

If not, activate them. Or if in a pinch, switch to using pr_alert() for
development.

Luis
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.kernelnewbies.org/pipermail/kernelnewbies/attachments/20150707/ca26df84/attachment.html 

Message not appearing in mesg

[Sébastien Hinderer]

Hi Luis,

Many thanks for your prompt and helpfulresponse!

> Do you have the relevant DEBUG macros activated in your kernel's
> configuration?

Perhaps not...

> https://www.kernel.org/doc/local/pr_debug.txt

Read this, thanks. But that has nothing to do with KConfigmacros, has
it?

> http://elinux.org/Debugging_by_printing
> 
> If not, activate them. Or if in a pinch, switch to using pr_alert() for
> development.

What surprises me is that I made sue the message appears inthe .ko file
and it was there,whereas it seems pr_debug discards its argument at
compile time. Or is it at execution time?

Thanks!

S?bastien.

Message not appearing in mesg

[Luis de Bethencourt]

On 7 July 2015 at 16:11, S?bastien Hinderer <Sebastien.Hinderer@ens-lyon.org
> wrote:

> Hi Luis,
>
> Many thanks for your prompt and helpfulresponse!
>
> > Do you have the relevant DEBUG macros activated in your kernel's
> > configuration?
>
> Perhaps not...
>
> > https://www.kernel.org/doc/local/pr_debug.txt
>
> Read this, thanks. But that has nothing to do with KConfigmacros, has
> it?
>
> > http://elinux.org/Debugging_by_printing
> >
> > If not, activate them. Or if in a pinch, switch to using pr_alert() for
> > development.
>
> What surprises me is that I made sue the message appears inthe .ko file
> and it was there,whereas it seems pr_debug discards its argument at
> compile time. Or is it at execution time?
>
> Thanks!
>
> S?bastien
>

Compile time. pr_debug() is meant only for development and discarded for
"production" builds.

pr_debug(), which is ordinarily an empty macro that discards its arguments
at compile time.
To enable debugging output, build the appropriate file with -DDEBUG by
adding

CFLAGS_[filename].o := -DDEBUG

That is the key part there. But it is good to also check the options you
have in:
make menuconfig-> Kernel Hacking

Enjoy,
Luis
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.kernelnewbies.org/pipermail/kernelnewbies/attachments/20150707/310e3572/attachment.html 

Message not appearing in mesg

[Shérab]

Thanks a lot Luis!
Everything is clear now.
Sh?rab.