Hi all, I just find in a document in the JDC that jdb has a start-up file, named jdb.ini, which can be used to store commands jdb commands - including breakpoint definitions. Couldn't that be used to build a quick "save-breakpoints" command? I guess that some manipulation of the user.home property would have to be done and probably stored on the prj.el file, but it shouldn't be hard to do. Too bad I'm still learning Emacs Lisp... Regards, Nascif http://developer.java.sun.com/developer/onlineTraining/JDCBook/running.html > Using Auto-Pilot > > One little known trick with jdb is the jdb startup file. jdb >automatically > looks for a file called jdb.ini in the user.home directory. If you >have > multiple projects, it is a good idea to set a different user.home >property > for each project when you start jdb. To start jdb with a jdb.ini >file in > the current directory, type the following: > > jdb -J-Duser.home=. > > The jdb.ini file lets you set up jdb configuration commands, such as > use, without having to enter the details each time jdb runs. The >following > example jdb.ini file starts a jdb session for the FacTest class. It > includes the Java platform sources on the source path list and >passes the > parameter 6 to the program. It then runs and stops at line 13, >displays the > free memory, and waits for further input. > > load FacTest > stop at FacTest:13 > use /home/calvin/java:/home/calvin/jdk/src/ > run FacTest 6 > memory > > Here is the output from the jdb.ini file execution: > > $ jdb -J-Duser.home=/home/calvin/java > Initializing jdb... > 0xad:class(FacTest) > Breakpoint set at FacTest:13 > running ... > Free: 662384, total: 1048568 > main[1] > Breakpoint hit: FacTest.compute (FacTest:13) > main[1] >
