| Author |
remote debugging with WTK emulator
|
Zandis Murāns
Ranch Hand
Joined: Aug 18, 2009
Posts: 174
|
|
I am getting stuck with getting jdeveloper's remote debugger to work with WTK emulator.
Here's how I run my WTK emulator:
When emulator is up and running, now I go to jdeveloper and try to connect JPDA remote debugger to port 8787... It connects fine and here's what I get in jdeveloper's console right after connecting:
Now, everything looks normal except if I set any break point in my midlet source, it just does not hit...
I've tried the same with netbeans debugger. Basicly, happens the same but extra message in netbeans console:
Yes, the jar file is packed with the same compiled midlet that is open in IDE and I set breakpoint at correct line.
Here's midlet source:
My breakpoint is set on line:
, but it just does not hit.
If I run my midlet in debug mode in Netbeans, debugging works just great.
If I do attach debugger to remote process, it just does not hit.
Any ideas how to get this working? :confused:
|
 |
Tim Holloway
Saloon Keeper
Joined: Jun 25, 2001
Posts: 14572
|
|
Any chance that your source code in the IDE isn't a match for the remote code?
This is a common problem when doing remote debugging. You set a breakpoint, but the breakpoint isn't where you thought it was because the line numbers for the code on the target machine don't match the line numbers on the debugging machine's source project.
|
Customer surveys are for companies who didn't pay proper attention to begin with.
|
 |
Zandis Murāns
Ranch Hand
Joined: Aug 18, 2009
Posts: 174
|
|
|
No, absolutley no chance of that...
|
 |
 |
|
|
subject: remote debugging with WTK emulator
|
|
|