The problem was basically that RIM's JDWP tool apparently wasn't fully compliant to the actual JDWP protocol, choosing instead to focus narrowly on its compatibility with Eclipse's debugging implementation. After some screwing around, it seems that RIM's JDWP tool expects something along the lines of jdb's "resume" command after the connection is established, otherwise it just keeps the simulator/device's JVM in a suspended state indefinitely.
Well, they promised to look at it, and this morning, roughly half a year later, their work was complete.
twindsor updated TOOL-118:Because, you know, "we want to meet you on your turf, we want to make it easy for you to use the tools you're already using". Thank you RIM, I love you too.
----------------------------
Status: Investigation (Closed) (was: Investigating)
Resolution: Fixed
JDWP with other development environments is no longer officially supported.
Only the use of JDWP with the Eclipse plugin is currently supported.
(to Tim Windsor, the developer liason who helped me initiate the issue: no offence, I understand that you're not the one making decisions such as what IDEs and dev environments to support. Thanks for your help.)
No comments:
Post a Comment