hi paul,

thanks for the prompt response.

you were right ... it was the firewall on my powerbook. turned it off and jdb listen/attach via socket works just fine!

emory


Hi Emory,

It would be nice to try to isolate the problems that you are
experiencing, in particular, to try to determine if the problems
are with jdb or with Emacs/JDEE or with the two in combination.
A way to do this is to try a few debugging sessions, using
the jdb command line interface alone. My suspicion is that the
problem is with jdb on the Macintosh and that you'll experience
the same problems if you try using jdb standalone.

Paul

Emory Smith writes:
hi,

ive been using jde for some time to debug webapps deployed locally on a
tomcat server and have consistently had a couple of annoying problems.


i set things up like so:

* start tomcat in listen mode ... open browser
* start emacs ... build and deploy to tomcat using jde-ant-build
* attach using jde-jdb-attach-via-socket
* set a breakpoint and refresh browser

at this point, everything works great -- breakpoint is hit, and jdb
runs without a hitch ... i do my stuff and then "cont" ... the browser
page finishes loading ...

9 times out of 10, thats the extent of my debugging session ... if i
want it to work again, i will have to quit tomcat at the least to get
any of it to work again (usually i have to actually kill off all
running java processes before tomcat will be able to connect to the
listen port again).  and even if tomcat connects, i can no longer set
breakpoints in any of my source files -- jdb will say "unable to set
breakpoint ... no code at line xxx".  ive tried everything i can think
of (clearing breakpoints, quiting jdb, detaching, closing browser, etc
) and in every possible order ... but it practically never works a
second time.  and when it does, jdb will invariably end up stepping
into some obscure java or tomcat class and i can type cont 200 times
without ever getting back to my own code ...

but as soon as i save files, quit jde, quit emacs, close my browsers,
quit tomcat, grep top for java and kill off any running java processes
(which are often very high cpu usage), wait for a little while, start
tomcat back up, start emacs, run ant remove/compile/install, start jdb
and attach to tomcat, set my breakpoint again, open the browser back up
and return to the page ... boom - it hits the breakpoint and i can
debug once again...


it seems like there should be a more efficient way to go about this, so
i was hoping someone might be able to point me in the right direction.
i apologize if this has been explained/discussed here already (though i
couldnt find anything like it in the archives).


also, im running mac os10.3.6 (though this has happened since 10.2.x)
on a powerbook g4.
(carbon) emacs 21.3.5, jdee 2.3.4, tomcat 5.0.27, jre 1.4.2, ant 1.6.1,


thanks for any suggestions anyone might have,
emory



Reply via email to