• Post Reply Bookmark Topic Watch Topic
  • New Topic
programming forums Java Mobile Certification Databases Caching Books Engineering Micro Controllers OS Languages Paradigms IDEs Build Tools Frameworks Application Servers Open Source This Site Careers Other Pie Elite all forums
this forum made possible by our volunteer staff, including ...
Marshals:
  • Tim Cooke
  • Campbell Ritchie
  • Ron McLeod
  • Junilu Lacar
  • Liutauras Vilda
Sheriffs:
  • Paul Clapham
  • Jeanne Boyarsky
  • Henry Wong
Saloon Keepers:
  • Tim Moores
  • Tim Holloway
  • Stephan van Hulst
  • Piet Souris
  • Carey Brown
Bartenders:
  • Jesse Duncan
  • Frits Walraven
  • Mikalai Zaikin

Eclipse remote debugging: Unable to install a breakpoint error

 
Greenhorn
Posts: 1
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
All,

I am using Eclipse to debug a remote Java application on a Solaris server and have built the class files using Ant options
<javac srcdir="${src.dir}" destdir="${build.dir}" debug="true" debuglevel="lines,vars,source" optimize="on" />

I ensured that the Eclipse environment had line numbers set on in preferences too (local debugging has never been a problem).

When I launched the JVM, I used these options: java -Xdebug -Xnoagent -Xrunjdwp dt_socket,server=y,address=8000 -Djava.compiler=NONE myApp

The error I get is: Attempting to install a breakpoint in the type Unload that has no line number attribute. Class files must be generated with the line number attributes. I have done some research and it appears that this might be an Eclipse bug. Any work arounds?
 
Ranch Hand
Posts: 539
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
What options did you specify to javac in Ant? If you passed any -g options (or anything else that alters debug information, this may be having an effect.

I guess it's also worth checking that this particular class is being compiled by Ant rather than using an old .class file - do you blow away your destination directory occasionally and start again from scratch?

Those are some other places to look anyway - I've yet to have a problem with Eclipse remote debugging though I'm on Windows (@ work).


-Tim
 
Ranch Hand
Posts: 493
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
Please pay particular attention to the Ant javac task below:

You have to specify debuglevel="lines,vars,source" to get the remote debugging to work right.
Regards.
Bharat

[ edited to add code tags - and &lt; for < ]
[ August 23, 2004: Message edited by: Jeanne Boyarsky ]
 
Greenhorn
Posts: 19
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
I had the same problem and I just added the debug option to javac ant task, and it was resolved. just add 'debug="true"' to javac and try again.
As you use Ant for the compilation, the settings of the eclipse does not take effect, this is why you have to add it to ant task explicitly.
 
This will take every ounce of my mental strength! All for a tiny ad:
Free, earth friendly heat - from the CodeRanch trailboss
https://www.kickstarter.com/projects/paulwheaton/free-heat
reply
    Bookmark Topic Watch Topic
  • New Topic