Paul Kinnucan wrote: > J�rgen Jatzkowski writes: > > Hi, > > > > I started using JDE as my favourite Java development environment ;) Now > > that I want to debug my application using JDEbug I come into some > > trouble when I step through the application: > > > > - I started the application outside Emacs (GNU Emacs 20.7.1) > > - returning to JDE (2.2.8) I attach via local host on port 2112 > > - I suspend the application, set some breakpoints and let the > > application continue > > - so far fine, the application hits one breakpoint and I step through it > > - after some "step over" commands the debugger seems to hang > > > > Is this a known phenomen? > > > > No. However, you should be aware that JDEbug is of alpha quality. > It has not received much attention over the last two years because > JDE users seemed more interested in other things like Ant support, > hierarchical projects, and field and method completion.
Oops, I thought that a debugging facility would help a lot in finding tricky bugs... > > I am now starting to devote most of my time to debugger support > so the situation should improve. My first priority is to provide > solid support for jdb because jdb is a more mature, though less > capable, debugger. I then plan to work on JDEbug. As I understood jdb is a reference implentation from Sun which has sme short comings. Wouldn't it make sense to invest into JDEBug ;) ? > > What this means is that I probably won't fix JDEbugs immediately. > > Of course, others can feel free to pitch in and help with JDEbug > if they have the time and inclination. My lisp skill is not to high, so I will try reproduce the situation described above. Maybe I will find the error. In the meantime I'm using IBM's JDK 1.3 which seems to work better. The next days will show if this remains true ;) J�rgen -- juergen jatzkowski [EMAIL PROTECTED] Linux, because rebooting is for adding hardware
