Scott,
seems like the DR0-DR3 are not set :
[0]kdb> md 0xa0f7bc94
0xa0f7bc94 00000007 00000001 00000003 00000000 ................
0xa0f7bca4 00000000 a0e1c70d a0e1c722 a0e1c72a .....Çá "Çá *Çá
0xa0f7bcb4 a0e6a7e0 a0e6a820 00000028 0000001c à§æ ¨æ (.......
0xa0f7bcc4 00000000 00000000 00000000 00000000 ................
0xa0f7bcd4 00000000 00000000 00000000 a0e1ca05 .............Êá
0xa0f7bce4 a0e1ca08 a0e1ca1a a0e1ca28 a0e1ca3c .Êá .Êá (Êá <Êá
0xa0f7bcf4 a0e1ca4e 00000000 00000000 03020100 NÊá ............
0xa0f7bd04 07060504 0b0a0908 0f0e0d0c 13121110 ................
[0]kdb> bpha 0xa0f7bc94 dataw 4
Forced Data Write BP #0 at 0xa0f7bc94
is enabled in dr0 for 4 bytes globally
[0]kdb> bl
[0]kdb> bl
Forced Data Write BP #0 at 0xa0f7bc94
([fwmod_smp.2.4.21.cp.i686]asm_fp_alt_ttl)
is enabled in dr0 for 4 bytes globally
[0]kdb> rd d
dr0 = 0x00000000 dr1 = 0x00000000 dr2 = 0x00000000 dr3 = 0x00000000
dr6 = 0xffff0ff0 dr7 = 0x00000400
Scott Lurndal wrote:
> On Wed, May 07, 2008 at 10:07:35AM +0300, Avi Nehori wrote:
>
>> I'm using 2.4.21 kernel (and also tried 2.6.18 with the same behavior).
>> the memory address is being written through a kernel module .
>> please see below :
>>
>> [0]kdb> md 0xa0f7bc94
>> 0xa0f7bc94 00000000 00000001 00000003 00000000 ................
>> [0]kdb> bpha 0xa0f7bc94 dataw 4
>> [0]kdb> go
>>
>>
>> the breakpoint is not called even though the memory address being changed:
>> [0]kdb> md 0xa0f7bc94
>> 0xa0f7bc94 00000064 00000001 00000003 00000000 d...............
>>
>>
>
> What does the 'bl' command show? It should show the debug register that
> the breakpoint was assigned to. You'll want to check it on all processors
> if you have a SMP machine.
>
> Please also use the 'rd d' command to display the contents of the debug
> registers on all processors.
>
> scott
>
>
> Scanned by Check Point Total Security Gateway.
>
>
---------------------------
Use http://oss.sgi.com/ecartis to modify your settings or to unsubscribe.
