won't stop trying to read bytes at bogus address when taking breakpoint

キャンセル
次の結果を表示 
表示  限定  | 次の代わりに検索 
もしかして: 

won't stop trying to read bytes at bogus address when taking breakpoint

ソリューションへジャンプ
1,222件の閲覧回数
bowerymarc
Contributor V

I've ported a K20F120M project from CW10.5 to KDE, first 1.0.1b and now 1.1.1 and both have the same behavior, where when I set a breakpoint (at the top of a task in FreeRTOS), it takes the breakpoint OK but then will not stop:

 

Read 4 bytes @ address 0x00024E08 (Data = 0x0330F240)

Read 4 bytes @ address 0x00024E08 (Data = 0x0330F240)

Read 4 bytes @ address 0x00024E08 (Data = 0x0330F240)

Read 4 bytes @ address 0x00024E08 (Data = 0x0330F240)

Read 4 bytes @ address 0x00024E08 (Data = 0x0330F240)

 

ad nauseum.  The only way to stop it is unplug the jlink debugger from the USB port.

 

Regardless of my code, I don't think the debugger should be doing... that!

ラベル(1)
タグ(2)
0 件の賞賛
返信
1 解決策
1,054件の閲覧回数
BlackNight
NXP Employee
NXP Employee

Hi Marc,

It could be the same issue as this one:

KDS debug for K22F120M in interrupt enviroment.

Can you add

set backtrace limit 20

to your debug configuration to see if this helps?

Erich

元の投稿で解決策を見る

0 件の賞賛
返信
2 返答(返信)
1,055件の閲覧回数
BlackNight
NXP Employee
NXP Employee

Hi Marc,

It could be the same issue as this one:

KDS debug for K22F120M in interrupt enviroment.

Can you add

set backtrace limit 20

to your debug configuration to see if this helps?

Erich

0 件の賞賛
返信
1,054件の閲覧回数
bowerymarc
Contributor V

hey that seems to have done it!  thanks a million!

I wonder why KDS falls down on that when CW seems fine?

0 件の賞賛
返信