From: Arno P. <ar...@pu...> - 2010-08-15 17:44:04
|
a little while ago I sent around a proposal over this mailing list for a proper debugging architecture. It would allow to debug a Java-based iPhone application from a standard Java debugger (such as Eclipse) and run the application on Apple's emulator or a real device (see my old message below). Needless to say that this is a lot of work and at this point all effort first goes into the new backend before coming back to debugging support. Arno --- Guys, we have been discussing a possible debugging architecture for XMLVM. There is currently no way to debug a program that was created with XMLVM in Apple's emulator or on an actual device. It is possible to debug on the Java side using XMLVM's emulation library for Cocoa Touch. However, this has two major disadvantages: problems often only materialize when you deploy your application on the actual device and it also requires us to keep pace with our own emulation library. We are getting more and more patches where people create new Java wrappers for Cocoa Touch API, but don't have the time and resources to provide an implementation for our Java-based emulation library. This approach does not scale. To solve both problems, we consider to focus our resources in a debugging architecture. Java supports remote debugging: http://java.sun.com/javase/technologies/core/toolsapis/jpda/index.jsp In particular, there is the so-called Java Debug Wire Protocol (JDWP): http://java.sun.com/j2se/1.5.0/docs/guide/jpda/jdwp-spec.html It defines an on-the-wire protocol between debugger and debugee (the application to be debugged). So, here is the idea we have been toying with: write a JDWP protocol engine in Java, cross-compile it to Objective-C, and deploy it (together with the application to be debugged) on the device. It should then be possible to connect via any standard Java Debugger to the application running on the device. Once we achieve that goal, it would enable us to do source-level debugging on the actual device and we no longer need to maintain our Java emulation library (since we would just leverage Apple's own emulator). We think that this is the way to go. Leaves us only with *a lot* of very tricky code. To implement the JDWP is no small feat. Anyone out there who has some experience with this? I have been poking around to see if there might already be a Java-based implementation of the JDWP, but I couldn't find one. Anyone? Arno --- On 8/14/10 4:52 PM, Damian wrote: > Isn't any way to debug the java code with the app running in the iphone > simulator? That was my main question. > A lot of java and .net projects that cross compile to other languages > manage to do it somehow, like monotouch or GWT. > What would be the way to make that possible with xmlvm? > > On Sat, Aug 14, 2010 at 9:22 AM, Troy Gaines <tro...@gm... > <mailto:tro...@gm...>> wrote: > > I just use the Apple iPhone simulator once I'm compiling in xCode. > You should be able to debug from there. > > > On Aug 14, 2010, at 12:51 AM, Damian <dam...@gm... > <mailto:dam...@gm...>> wrote: > >> Well, but there is no way to debug the code while running on apple >> simulator, right? Am I missing something? >> thanks! >> >> On Sun, Jul 25, 2010 at 7:02 PM, Panayotis Katsaloulis < >> <mailto:pan...@pa...>pan...@pa... >> <mailto:pan...@pa...>> wrote: >> >> >> On 24 Ιουλ 2010, at 6:34 π.μ., Damian Troncoso wrote: >> >> > Well, I'm finding myself blocked by the emulator >> capabilities, and I >> > think that using it maybe is not the best idea. >> > Is there any way to use apple emulator and be able to debug >> somehow? >> > Anyone has taken the approach of not using xmlvm emulator >> and using >> > apple's one or a real device? Could I have better luck this way? >> > The problem I find with xmlvm emulator is that most of apple >> libraries >> > are not implemented, and I think doing so is not practical >> at all. >> > Besides that, I don't think it's uncommon to find problems >> in apple >> > emulator that wasn't in xmlvm one, because the code is not >> the same. >> > So finding a way to debug in the actual device would be >> absolutely >> > useful and there would be no need to put so much effort on xmlvm >> > emulator and libs. Am I right? >> > >> > Any help or idea will be greatly appreciated. >> > Damian >> >> >> try this command: >> >> java -jar xmlvm.jar --out=OUT_DIR --app-name=NAME >> --skeleton=iphone >> >> and of course replace OUT_DIR and NAME with actual parameters. >> Then open the created project in Netbeans under OS X. >> Don't forget to change target form Netbeans to Xcode >> ------------------------------------------------------------------------------ >> This SF.net <http://SF.net> email is sponsored by Sprint >> What will you do first with EVO, the first 4G phone? >> Visit <http://sprint.com/first>sprint.com/first >> <http://sprint.com/first> -- >> <http://p.sf.net/sfu/sprint-com-first>http://p.sf.net/sfu/sprint-com-first >> _______________________________________________ >> xmlvm-users mailing list >> <mailto:xml...@li...>xml...@li... >> <mailto:xml...@li...> >> <https://lists.sourceforge.net/lists/listinfo/xmlvm-users>https://lists.sourceforge.net/lists/listinfo/xmlvm-users >> >> >> ------------------------------------------------------------------------------ >> This SF.net <http://SF.net> email is sponsored by >> >> Make an app they can't live without >> Enter the BlackBerry Developer Challenge >> http://p.sf.net/sfu/RIM-dev2dev >> _______________________________________________ >> xmlvm-users mailing list >> xml...@li... >> <mailto:xml...@li...> >> https://lists.sourceforge.net/lists/listinfo/xmlvm-users > > > > > ------------------------------------------------------------------------------ > This SF.net email is sponsored by > > Make an app they can't live without > Enter the BlackBerry Developer Challenge > http://p.sf.net/sfu/RIM-dev2dev > > > > _______________________________________________ > xmlvm-users mailing list > xml...@li... > https://lists.sourceforge.net/lists/listinfo/xmlvm-users |