Kernel 2.4.20
I applied the 2.4.19 patches (didn't see one for 2.4.20 in the downloads
area), only 2 files had minor issues, that were fixed by hand.
./kernel/ksyms.c.rej
./drivers/usb/usbkbd.c.rej
After I load my kernel module, I set a breakpoint in a kernel function, say
Kdb> bp printk
It shows me that the breakpoint#0 is set.
Then I type
Kdb> go
When the driver or any kernel function calls printk, I notice the debugger
prompt. I can look at back trace etc at this time. Then I do "go" again, on
any future printk's I don't see the debugger break into and giving me a kdb
prompt.
Now I can manually break in using the "break" key, and then delete the
breakpoint and set a new one "bp printk" again. Now I see the break happen
and kdb prompt appear again.
Justfyi, when I applied the gdb patches instead of the kdb patches, I see
the exact same behavior on 2.4.20.
ashokr
-----Original Message-----
From: Keith Owens [mailto:kaos@xxxxxxx]
Sent: Wednesday, December 04, 2002 3:51 PM
To: Raj, Ashok
Cc: 'kdb@xxxxxxxxxxx'
Subject: Re: debug issues
On Wed, 4 Dec 2002 14:59:11 -0800 ,
"Raj, Ashok" <ashok.raj@xxxxxxxxx> wrote:
>This message is in MIME format. Since your mail reader does not understand
>this format, some or all of this message may not be legible.
Please send only plain text, not html+text.
>Not sure if anyone has noticed it. Iam seeing the same issues when I use
>either the kdb or the gdb patches for any kernel 2.4.18 and above.
>
>When I set breakpoints, I see it hit once, but never hits the next time. If
>I delete and set the breakpoint again, it seems to work again. (just one
>more time)
Insufficient details to diagnose what problem, if any, you have. Which
kernel? Which kdb patches? What commands? What output?
|