Slashdev Support Forum

A place to ask questions about projects and posts on the Slashdev blog.

1. benvd
   Member

   Hi. This is not directly related to your blogposts (since you use virtualised jdwp, and not bjdwp (i.e. the Barry implementation of jdwp)), but I figured I'd ask it here anyway, since you seem to know a lot about BlackBerry development on non-Windows OSes.

   After I run my app on a (physical) device, I start "bjdwp localhost 8000". After that, I can connect to this using "jdb -connect com.sun.jdi.SocketAttach:hostname=localhost,port=8000". After connecting, though, nothing seems to happen until I enter the resume command in jdb. Then it's smooth sailing.

   I'd love to be able to debug using eclipse since it's a much more comfortable environment. I created a new debug configuration for this, as follows: a Remote Java Application with connection type = "Socket Attach", host = "localhost" and port = "8000". In other words, the same kind of connection as the jdb command. This doesn't work, however -- it keeps trying to connect.

   Now, I assume this is because I need to do a resume, like I needed to do with jdb, but I can't do that from within eclipse (the resume button is greyed out).

   Any suggestions?

   Posted 1 year ago #

2. jiggak
   Key Master

   Unfortunately I haven't used bjdwp at all. You might try emailing the Barry list. The folks there are very receptive and helpful.

   Nicolas is the guy who created bjdwp and as far as I know it's unfinished. Breakpoints won't work neither will inspecting object references. I think about the only thing this would be useful for is seeing the standard output (ie: System.out.println() output).

   I wouldn't be surprised if adding this feature to auto-resume would be a simple thing to add so if you ask nicely Nicolas might be able to knock it out pretty quick. Or you can dig into the barry code.

   Posted 1 year ago #

3. benvd
   Member

   Oops, kind of lost track of this for a while.

   Apparently you can add commands to ~/.jdbrc which will be automatically executed when starting jdb. So I just did echo "resume" >> ~/.jdbrc and this minor annoyance was gone.

   OK, so my assumptions were wrong and barry just doesn't support step-by-step debugging. Ah well, I never got that to work reliable in Windows (with official tools) either, so just having stdout is not that bad. :)

   Posted 1 year ago #

RSS feed for this topic

Reply

You must log in to post.