Kerry Alt wrote:
> For some reason when trying to debug certain files, I get the "No code
> or optimized error". I'm stumped, as the classpath and debug-source
> path are apparently correct. I'm using the same prj.el files on Solaris
> 2.6 (xemacs 20.4) and Win95, NT/97 emacs 20.3.1. For example, db-source
> looks like:
>
> Db Source Directories: *
> [INS] [DEL] Path: /home/pima1/kalt/cm/manager/interfaces/
> [INS] [DEL] Path: /home/pima1/kalt/cm/physicsmodels/interfaces/
> [INS]
>
> Now when I try to set breakpoints for a file in
> /home/pima1/kalt/cm/physicsmodels/interfaces/, I get:
> No code at line 77, or class is optimized.
> No code at line 70, or class is optimized.
> No code at line 149, or class is optimized.
> No code at line 71, or class is optimized.
> No code at line 124, or class is optimized.
>
> But if I try to set a break in: /home/pima1/kalt/cm/manager/interfaces/,
> I get:
>
> Breakpoint set at cm.manager.interfaces.BlastPanel:40
>
> On both platfroms, all files are compiled with jikes -g +E, cc-mode
> version is 5.19, JDE version is 2.1.5, and .emacs and prj.el are
> attached.
If you're using inner classes, breakpoints don't work right in JDE. You have to spell
them out. JDB wants you to tell it the entire name of the class, so for example you
may have to do something like:
stop at cm.manage.interfaces.BlastPanel$NamedInnerClass:40
or if you have anonymous inner classes, they are numbered; the first is $0, $1, $2,
etc:
stop at cm.manage.interfaces.BlastPanel$0:40
would try and set a breakpoint in the first anonymous inner class in BlastPanel.java
at line 40 of the file
