when breakpoint was hit first time, target board replied blank callstack over jdwp. (it works well with intellij)
0 posts in topic
Flat View  Flat View
TOPIC ACTIONS:
 

Posted By:   Sang_Kim
Posted On:   Wednesday, April 15, 2009 10:34 PM

eclipse was connected to target board over remote debugging (jdwp) And when a breakpoint was hit first time, callstack was blank on suspended thread and "this" variable was empty too and started working since 2nd hitting on same breakpoint. It works well with intellij under same environment (e.g. network configuration, jre version etc) I sniffered jdwp packets using wireshark and it looks JVM (target board) replied back with blank callstack (no error) as follows. So it maybe a Java Virtual Machine issue. But I wonder if someone knows if it is eclipse bug (as intellij works) or is there workaound to work with eclipse. A.   More>>


eclipse was connected to target board over remote debugging (jdwp)



And when a breakpoint was hit first time, callstack was blank on suspended thread and "this" variable was empty too and started working since 2nd hitting on same breakpoint.



It works well with intellij under same environment (e.g. network configuration, jre version etc)



I sniffered jdwp packets using wireshark and it looks JVM (target board) replied back with blank callstack (no error) as follows.



So it maybe a Java Virtual Machine issue.
But I wonder if someone knows if it is eclipse bug (as intellij works) or is there workaound to work with eclipse.



A. Success case



Debugger ---> target (Command packet)
Length : 0x00000017
Id : 0x000001dc
Flag : 0x00
Command set : 0x0b (ThreadReference command set)
Command : 0x06 (Frames command - returns the current call stack of a suspended thread.)
Data : 2fbe789400000000ffffffff



Target ---> debugger (Reply packet)
Length : 0x00000231
Id : 0x000001dc
Flag : 0x80
Error code : 0x0000
Data : 0000001a3b080180012f999c8c0359500000000000000000003b0801e4012f999ca4032e1000000000000000002f3b08023c012f999cac0323f00000000000000000023b0802a0012f999cb4031cc00000000000000000183b0802f4012f999cbc0217500000000000000000043b08034c012f999cc4002d700000000000000000013b0803a4012f999cc4002d600000000000000000023b080428012f999ccc019f4000000000000000004a3b080484012f999ccc019f5000000000000000000a3b0804e0012f999cac0324000000000000000000083b080538012f999cd40318100000000000000000093b080590012f999cd40318200000000000000000023b0805fc012f999cd40317400000000000000000593b080650012f999cdc031c900000000000000000693b0806ac012f999ce4019d300000000000000000133b080710012f999cb4031cc00000000000000000183b080764012f999cbc0217500000000000000000043b0807bc012f999cc4002d700000000000000000013b080814012f999cc4002d600000000000000000023b080898012f999ccc019f4000000000000000004a3b0808f4012f999ccc019f5000000000000000000a3b080950012f999cec031b200000000000000000083b0809ac012f999cf4031b6000000000000000000e3b080a08012f999ce4019d300000000000000000133b080a5c012f999cfc019ce000000000000000001c3b080ab0012f999bfc00107000000000000000000b



B. Failure case



Debugger ---> target (Command packet)
Length : 0x00000017
Id : 0x00000211
Flag : 0x00
Command set : 0x0b (ThreadReference command set)
Command : 0x06 (Frames command - returns the current call stack of a suspended thread.)
Data : 2fbe789c00000000ffffffff



Target ---> debugger (Reply packet)
Length : 0x0000000b
Id : 0x00000211
Flag : 0x80
Error code : 0x0000 (no error)
Data : 0xd

   <<Less
About | Sitemap | Contact