linux-kernel - Re: How to see kernel pr

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <20100227120630.GA18061@a1.tnic>
Date:	Sat, 27 Feb 2010 13:06:30 +0100
From:	Borislav Petkov <petkovbb@...glemail.com>
To:	reg@....com
Cc:	linux-kernel@...r.kernel.org
Subject: Re: How to see kernel pr_err error messages.

From: reg@....com
Date: Sat, Feb 27, 2010 at 03:11:03AM -0700

> Im looking at some kernel code, and there are 'pr_err' error messages in
> it that would help me discover my problem.
> 
> However I dont see them printing anywhere.
> 
> What do I have to do to see these error messages?

Take a look at 'ignore_loglevel' and 'loglevel' kernel parameters in
<Documentation/kernel-parameters.txt> depending on what exactly you want
to achieve.

> A search with GOOGLE  and a grep of the code wasnt too useful, but
> it seems possible that I need to set
> 
>     #define CONFIG_DEBUG
> 
> Is that true?  I see a lot of <something>_DEBUGs in the .config file
> but no simple CONFIG_DEBUG that is commented out.

I think this is referring to pr_debug() calls. Those get called when you
add

#define DEBUG

to the file containing them. Otherwise they're optimized away.

-- 
Regards/Gruss,
Boris.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/