Hi,
I find this bug in KDB patch "kdb-v2.5-2.4.19" together with
pristine kernel 2.4.19.
This bug doesn't happen on "bp" or "bpa".
The steps to reproduce:
1. Enter KDB by key "Pause"
2. bph printk (or bpha printk)
3. go
4. insmod testkdb.o ( This is my test module, which prints messages
by "printk" in the initialization routine. Compile file "testkdb.c" before
do the test.)
The result:
Fail to trap into KDB at the breakpoint.
Regards.
Sonic Zhang
File "testkdb.c"
-----------------------------------------------
#include <linux/kernel.h>
#include <linux/module.h>
char testkdbmsg[ ]="This is a test!"
int testkdbbph;
int testkdbbph2;
/*=========================
init the module
==========================*/
int init_module(void)
{
testkdbbph = 0x34342;
printk("%s\n",testkdbmsg);
return 0;
}
/*=========================
cleanup the module
==========================*/
void cleanup_module(void)
{
testkdbbph2 = testkdbbph;
printk("%s\n",testkdbmsg);
}
-----------------------------------------------
