> The reason that you don't get a cursor is that you commented out all the
> essential code required to allow Emacs to track the location of
> the current
> breakpoint!! The JDE extracts breakpoint locations from the debugger's
> output, using the filter functions you've commented out.
I had to comment out those lines because otherwise I got the message:
Symbol's value as variable is void: jde-db-marker-filter
I can't figure out why. I've even tried to load-file jde-db.el, where
jde-db-marker-filter is defunned, but I still get that message when I run my
command.
> >
> >Can you make it easier to add arguments (i.e. -Xdebug) to the vm
> when bsh is
> >launched? In particular when your bsh functions are called from
> other lisp
> >functions.
> >
>
> Yes.
Great. Thanks.
>
> >Also, Can you add a function to start the debugger given a hostname and a
> >password? This way, it would be easy for elisp programmers to
> write little
> >methods to launch there apps using java -Xdebug, and start the
> debugger in
> >another window. In the attached code you will see my attempt at such a
> >function, but as I mentioned earlier, it doesn't quite work.
> >
>
> Yes. I actually do something like this to enable applet debugging. You
> might want to take a look at it. The code is in jde-db.el.
I'll take a look at this. Hopefully it could get me past my problem above.
>
> That being said, I think an easier approach at bsh/debugger integration
> might be to launch the debugger from within the BeanShell. At
> least that is
> the approach I have planned on taking. However, at this point, I am
> reluctant to undertake any serious work on the debugger until we get a
> replacement for jdb that is geared to working with the JDE. As you may be
> aware, Sun itself has volunteered to assist me in creating such a
> debugger,
> to the point of even offering to hire a summer intern to adapt Sun's new
> version of jdb to work with the JDE.
Yes, I saw messages to that effect on the list. I'm looking forward to
better debugging support.
I'm not sure what you mean by launching the debugger from beanshell. My
first thought was to simply run beanshell with jdb instead of javaw. But I
wanted the output from the two to be in seperate windows. In particular, if
beanshell was running in jdb, I was afraid of losing the abiity to hit
[ctrl]-[up arrow] to repeat the last command in beanshell.
Thanks.
-Dave
