(gdb) n
Cannot remove breakpoints because program is no longer writable.
Further execution is probably impossible.
1325pr_info("Run %s as init process\n", init_filename);
(gdb)
Cannot remove breakpoints because program is no longer writable.
Further execution is probably impossi
:
> >>
> >> >>> On Wed, Mar 15, 2017 at 10:31 AM, Tobin C. Harding <m...@tobin.cc>
> >> >>> wrote:
> >> >>> > why does calling pr_debug() with more than one argument cause a
> >> >>> > sparse
>
g <m...@tobin.cc> wrote:
>> >>> > why does calling pr_debug() with more than one argument cause a sparse
>> >>> > warning?
>> >>> >
>> >>> > drivers/mmc/core/sdio_io.c:70:9: error: unknown field name in
&
On Wed, Mar 15, 2017 at 12:12:48PM +0100, Bjørn Mork wrote:
> Alexander Kapshuk <alexander.kaps...@gmail.com> writes:
>
> >>> On Wed, Mar 15, 2017 at 10:31 AM, Tobin C. Harding <m...@tobin.cc> wrote:
> >>> > why does calling pr_debug() with more tha
Alexander Kapshuk <alexander.kaps...@gmail.com> writes:
>>> On Wed, Mar 15, 2017 at 10:31 AM, Tobin C. Harding <m...@tobin.cc> wrote:
>>> > why does calling pr_debug() with more than one argument cause a sparse
>>> > warning?
>>> >
>>
On Wed, Mar 15, 2017 at 12:40 PM, Tobin C. Harding <m...@tobin.cc> wrote:
> On Wed, Mar 15, 2017 at 12:01:39PM +0200, Alexander Kapshuk wrote:
>> On Wed, Mar 15, 2017 at 10:31 AM, Tobin C. Harding <m...@tobin.cc> wrote:
>> > why does calling pr_debug() with more th
On Wed, Mar 15, 2017 at 12:01:39PM +0200, Alexander Kapshuk wrote:
> On Wed, Mar 15, 2017 at 10:31 AM, Tobin C. Harding <m...@tobin.cc> wrote:
> > why does calling pr_debug() with more than one argument cause a sparse
> > warning?
> >
> > drivers/mmc/core/sdio_io.
On Wed, Mar 15, 2017 at 10:31 AM, Tobin C. Harding <m...@tobin.cc> wrote:
> why does calling pr_debug() with more than one argument cause a sparse
> warning?
>
> drivers/mmc/core/sdio_io.c:70:9: error: unknown field name in initializer
>
> sdio_io.c:70:
> pr_debug(&qu
why does calling pr_debug() with more than one argument cause a sparse
warning?
drivers/mmc/core/sdio_io.c:70:9: error: unknown field name in initializer
sdio_io.c:70:
pr_debug("SDIO: Enabling device %s...\n", sdio_func_id(func));
What can we do about this?
tha
On Tue, May 10, 2016 at 09:33:46AM +0200, Greg KH wrote:
> Please read Documentation/dynamic-debug-howto.txt
thanks Greg, your are a gentleman.
tobin
___
Kernelnewbies mailing list
Kernelnewbies@kernelnewbies.org
On Tue, May 10, 2016 at 05:21:35PM +1000, Tobin Harding wrote:
> pr_debug messages do not appear in dmesg output (or via cat /proc/kmsg). I
> have
> set console level to 8 (cat /proc/sys/kernel/printk -> 8 1 4 8).
>
> Any suggestions please?
Please read Documentation/dynam
pr_debug messages do not appear in dmesg output (or via cat /proc/kmsg). I have
set console level to 8 (cat /proc/sys/kernel/printk -> 8 1 4 8).
Any suggestions please?
--
thanks,
Tobin.
___
Kernelnewbies mailing list
Kernelnewbies@kernelnewbies.
I am using journalctl -kf or journalctl -k
to see kernel log messages.
However, messages of pr_debug are not shown by this commands.
Is there some way to view pr_debug kernel messages with journalctl -k ?
regards,
Kevin
___
Kernelnewbies mailing
Kevin Wilson wkev...@gmail.com writes:
I am using journalctl -kf or journalctl -k
to see kernel log messages.
However, messages of pr_debug are not shown by this commands.
Is there some way to view pr_debug kernel messages with journalctl -k ?
pr_debug messages is usually an empty macro
Thomas Gummerer t.gumme...@gmail.com writes:
Kevin Wilson wkev...@gmail.com writes:
I am using journalctl -kf or journalctl -k
to see kernel log messages.
However, messages of pr_debug are not shown by this commands.
Is there some way to view pr_debug kernel messages with journalctl -k
hi all:
I'm confused with pr_debug. My codes is:
###
#include linux/module.h
#include linux/kernel.h
static int __init init_page_dir(void)
{
pr_debug(Hello world\n);
return 0;
}
static void __exit exit_page_dir(void)
{
pr_debug(\nGoodbye
On Wed, Jun 25, 2014 at 02:09:40PM +0800, lx wrote:
hi all:
I'm confused with pr_debug. My codes is:
###
#include linux/module.h
#include linux/kernel.h
static int __init init_page_dir(void)
{
pr_debug(Hello world\n);
return 0
refer this :https://www.kernel.org/doc/local/pr_debug.txt
On 06/25/2014 11:39 AM, lx wrote:
hi all:
I'm confused with pr_debug. My codes is:
###
#include linux/module.h
#include linux/kernel.h
static int __init init_page_dir(void)
{
pr_debug
On Tue, Jun 24, 2014 at 11:09 PM, lx lxlenovos...@gmail.com wrote:
hi all:
I'm confused with pr_debug. My codes is:
###
#include linux/module.h
#include linux/kernel.h
static int __init init_page_dir(void)
{
pr_debug(Hello world\n);
use
On Wed, Jun 25, 2014 at 11:39 AM, lx lxlenovos...@gmail.com wrote:
hi all:
I'm confused with pr_debug. My codes is:
###
#include linux/module.h
#include linux/kernel.h
static int __init init_page_dir(void)
{
pr_debug(Hello world\n
Varka Bhadram varkabhad...@gmail.com writes:
refer this :https://www.kernel.org/doc/local/pr_debug.txt
That seems a little outdated since it doesn't mention the extremely
useful dynamic debug feature. So please read
https://www.kernel.org/doc/Documentation/dynamic-debug-howto.txt
as well.
The
thank you.
But the Makefile is so simple and Not use cc.
#
obj-m := task_01.o
KDIR:=/lib/modules/`uname -r`/build
PWD:=$(shell pwd)
default:
echo $KDIR
$(MAKE) -C $(KDIR) M=$(PWD) modules
#
So, how to add CFLAGS?
Thank you. I fix it
EXTRA_CFLAGS += -DDEBUG
2014-06-25 17:50 GMT+08:00 Varka Bhadram varkabhad...@gmail.com:
On 06/25/2014 03:17 PM, lx wrote:
thank you.
But the Makefile is so simple and Not use cc.
#
obj-m := task_01.o
CFLAGS_task_01.o :=
I'm on Debian here and I don't really get pr_debug and printk(KERN_DEBUG
...). Let's stick to pr_debug.
I have DYNAMIC_DEBUG enabled and
root@laptop:/proc/sys/kernel# cat /proc/sys/kernel/printk
7 7 1 7
I write a module with pr_debug's. I load the module and I *don't* see
Hi Martin,
On Wed, Apr 16, 2014 at 2:13 PM, Martin Kepplinger mart...@posteo.de wrote:
I'm on Debian here and I don't really get pr_debug and printk(KERN_DEBUG
...). Let's stick to pr_debug.
I have DYNAMIC_DEBUG enabled and
root@laptop:/proc/sys/kernel# cat /proc/sys/kernel/printk
7 7
Am 2014-04-16 11:00, schrieb Arun KS:
Hi Martin,
On Wed, Apr 16, 2014 at 2:13 PM, Martin Kepplinger mart...@posteo.de wrote:
I'm on Debian here and I don't really get pr_debug and printk(KERN_DEBUG
...). Let's stick to pr_debug.
I have DYNAMIC_DEBUG enabled and
root@laptop:/proc/sys
Hi Martin,
On Wed, Apr 16, 2014 at 2:46 PM, Martin Kepplinger mart...@posteo.de
wrote:
Am 2014-04-16 11:00, schrieb Arun KS:
Hi Martin,
On Wed, Apr 16, 2014 at 2:13 PM, Martin Kepplinger mart...@posteo.de
wrote:
I'm on Debian here and I don't really get pr_debug and printk(KERN_DEBUG
really get pr_debug and
printk(KERN_DEBUG
...). Let's stick to pr_debug.
I have DYNAMIC_DEBUG enabled and
root@laptop:/proc/sys/kernel# cat /proc/sys/kernel/printk
7 7 1 7
This shows the console log level.
This file controls the traffic to console. But all the log
Martin,
I'm not sure did you enable DDEBUG when compiling your module ?
pr_debug() macro is discarded if you omit DEBUG in compile time
A sample Makefile which enable pr_debug() :
obj-m += my_modue.o
KDIR ?= /lib/modules/`uname -r`/build
CFLAGS_my_module.o := -DDEBUG
all:
make -C $(KDIR) M
Am 16.04.2014 13:43 schrieb Denis Pithon:
Martin,
I'm not sure did you enable DDEBUG when compiling your module ?
pr_debug() macro is discarded if you omit DEBUG in compile time
A sample Makefile which enable pr_debug() :
obj-m += my_modue.o
KDIR ?= /lib/modules/`uname -r`/build
Hello Martin and Dennis,
On Wed, Apr 16, 2014 at 5:27 PM, Martin Kepplinger mart...@posteo.dewrote:
Am 16.04.2014 13:43 schrieb Denis Pithon:
Martin,
I'm not sure did you enable DDEBUG when compiling your module ?
pr_debug() macro is discarded if you omit DEBUG in compile time
On Wed, 16 Apr 2014 13:57:07 +0200, Martin Kepplinger said:
I'd like to just read all pr_debug() messages like pr_info().
Did you consider, um, I don't know? Just building a kernel that
doesn't have CONFIG_DYNAMIC_DEBUG turned on?
Or you could read Documentation/dynamic-debug-howto.txt
is not a problem but a syslog feature :)
http://www.rsyslog.com/doc/rsyslog_conf_filter.html
On Wed, Apr 16, 2014 at 1:57 PM, Martin Kepplinger mart...@posteo.dewrote:
Am 16.04.2014 13:43 schrieb Denis Pithon:
Martin,
I'm not sure did you enable DDEBUG when compiling your module ?
pr_debug
I am using 'pr_debug()' to print debug statements. But I don't see
anything in my serial console. But when I use pr_info(), I see the
debug statements.
Do I need to do anything to see pr_debug()?
Thank you.
___
Kernelnewbies mailing list
Kernelnewbies
On Wed, Feb 26, 2014 at 11:35:23AM -0800, m silverstri wrote:
I am using 'pr_debug()' to print debug statements. But I don't see
anything in my serial console. But when I use pr_info(), I see the
debug statements.
Do I need to do anything to see pr_debug()?
add this to the top of the file
On Wed, 26 Feb 2014 11:35:23 -0800, m silverstri said:
I am using 'pr_debug()' to print debug statements. But I don't see
anything in my serial console. But when I use pr_info(), I see the
debug statements.
Do I need to do anything to see pr_debug()?
You probably need a #define DEBUG. Also
07:31:25 ( +09:00 )
To : m silverstri michael.j.silvers...@gmail.com
Cc : kernelnewbies kernelnewbies@kernelnewbies.org
Subject : Re: How to use pr_debug
On Wed, 26 Feb 2014 11:35:23 -0800, m silverstri said:
I am using 'pr_debug()' to print debug statements. But I don't see
anything in my serial
valdis.kletni...@vt.edu
Sent : 2014-02-27 07:31:25 ( +09:00 )
To : m silverstri michael.j.silvers...@gmail.com
Cc : kernelnewbies kernelnewbies@kernelnewbies.org
Subject : Re: How to use pr_debug
On Wed, 26 Feb 2014 11:35:23 -0800, m silverstri said:
I am using 'pr_debug()' to print debug statements
38 matches
Mail list logo
