On Mon, 2007-10-22 at 11:54 +1000, Cameron McCormack wrote: > Hi all. > > I want to use Eclipse debug my application running on Classpath. I > tried to follow the instructions at > > http://developer.classpath.org/mediation/ClasspathHackingWithEclipse > > to set up my environment, but Iʼve run into a couple of stumbling > blocks. > > I tried first with jamvm. All of the steps in the wiki page work, but > when it comes to debugging my application, jamvm complains that it > doesnʼt know what -Xdebug means. So I patched jamvm to ignore that (and > -Xnoagent), but Eclipse also passed a > -Xrunjdwp:transport=dt_socket,suspend=y,address=localhost:37927 > command line argument, and that looks like something that couldnʼt be > just ignored to get debugging working properly. Does jamvm support > debugging from Eclipse? No it does not. > > I also tried with cacao, grabbing the sources from the hg repository. > Again, the steps in the wiki succeeded, but when it came to debugging, > Eclipse tells me: > > main: lt_dlsym failed: /usr/local/jdk1.6.0_03/jre/lib/i386/client/libjvm.so: undefined symbol: vm_createjvm > > Anybody know what this could be? (I presume itʼs mentioning jdk1.6.0_03 > because thatʼs VM that Eclipse itself is running on.) Seems like some environment variable is set, like LD_LIBRARY_PATH, that points to /usr/local/jdk1.6.0_03/jre/lib/i386/client/. The CACAO binary tries to load the libjvm.so found but it's the one from Sun. That's why the lt_dlsym fails. - twisti
