• 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 all forums
this forum made possible by our volunteer staff, including ...
  • Campbell Ritchie
  • Paul Clapham
  • Ron McLeod
  • Bear Bibeault
  • Liutauras Vilda
  • Jeanne Boyarsky
  • Junilu Lacar
  • Henry Wong
Saloon Keepers:
  • Tim Moores
  • Stephan van Hulst
  • Jj Roberts
  • Tim Holloway
  • Piet Souris
  • Himai Minh
  • Carey Brown
  • salvin francis

JavaRebel - Eclipse & Debugging - Missing line numbers

Posts: 14
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Have just downloaded JavaRebel after getting the mailshot from the ranch. If it can sort out my biggest annoyance with Eclipse...having to restart tomcat several times a day during development....I'll be happy.

But, I have a problem with debugging. Start from the Eclipse and I get the JavaRebel message in the console. I then add a breakpoint in MyClass.java. When the code executes I get an error pop-up from Eclipse when the breakpoint is hit saying:

"Unable to install breakpoint in path.to.class.MyClass$$A$736f0a9e due to missing line number attributes. Modify compiler options to generate line number attributes."

Click OK and I can step through the code with the debugger anyway. But, once the code has executed successfully, as soon as I touch the class the breakpoint was in and save (even just adding/removing a space) I get the "Hot Code Replaced Failed" popup.

I have the option to generate line numbers for debugging checked in the compiler properties in Eclipse.

Any ideas? Fully accept that I may just be a plank and haven't configured something correctly :-)

Eclipse 3.3.1 with MyEclipse 6.0.1
Tomcat 5.5
JDK 1.5
[ August 12, 2008: Message edited by: Adam Brundrett ]
JavaRebel Support
Posts: 17
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Hi Adam,

You can ignore the messages produced by Eclipse for such errors. Eclipse will get confused about the updates and you will even see the red little icons in the stack window but everything works fine.

See the FAQ for more details.
Adam Brundrett
Posts: 14
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Thanks for the reply.

Onwards with the evaluation then
I've been selected to go to the moon! All thanks to this tiny ad:
Thread Boost feature
    Bookmark Topic Watch Topic
  • New Topic