Re: jde-complete generates imports I don't want
Paul Kinnucan [EMAIL PROTECTED] writes: Based on this experiment, I believe that JDEE 2.3.4 handles the test case that you presented correctly within its limitations, i.e., that it only imports and completes things that are on the classpath. I verified that the same thing happens with the test case in my environment. I didn't realize that one has to compile both *.java files to make it work. So now I need to work on getting a test case that demonstrates the problem: the problem still happens with the real code that I'm editing. One difference between the test case and the real code is that the real code is compiled, jared (jarred? jar'd?) and the *.jar file is in $CLASSPATH. But the *.class files are NOT in $CLASSPATH. Another difference is that the real project has a prj.el file whereas the test case didn't have one. I'm sure that this is pilot error; I just don't know what I'm doing wrong. Kai
bsh error
Hello, I recently upgrade my system from Mandrake 10 to Mandrake 10.1. Jde and bsh worked on Mandrake 10 and now Jde works but when i try to interprete something (e.g in order to import something), i have the following error : Beanshell expression evaluation error. Expression: jde.util.JdeUtilities.getQualifiedName(JTextField); Error: // Error: EvalError: Class or variable not found: jde.util.JdeUtilities : at Line: 2 : in file: unknown file : jde .util .JdeUtilities .getQualifiedName ( JTextField ) [2 times] bsh: Beanshell eval error. See messages buffer for details. Could you help me. thanks. Nic
jde and emacs memory usage
Right now my Emacs process is using 127 Megs of memory. While the *jde-beanshell-scratch* buffer size is 1239491, and another buffer I have is also just over 1 Meg, the total sum of all my buffers is still only a few megabytes, I definitely am not consuming anywhere near 100 megabytes in buffers. What could be taking up all the memory? How do I free it up? I've had emacs run out of memory a few times in the last couple of weeks. Raul
Re: jde and emacs memory usage
The jde-beanshell-buffer is something that jde-usages to record the output of bsh. It's like a *Messages* buffer for the beanshell, but unlike *Messages* it doesn't clear out old entries. Adding the equivalent of message-log-size for this buffer is on my to-do list. You can delete the buffer at any point without any adverse effects. The next time jde-usages makes a call to bsh it will create the buffer if it does not exist. Suraj On Thu, 18 Nov 2004 11:53:11 -0800, Raul Acevedo [EMAIL PROTECTED] wrote: Right now my Emacs process is using 127 Megs of memory. While the *jde-beanshell-scratch* buffer size is 1239491, and another buffer I have is also just over 1 Meg, the total sum of all my buffers is still only a few megabytes, I definitely am not consuming anywhere near 100 megabytes in buffers. What could be taking up all the memory? How do I free it up? I've had emacs run out of memory a few times in the last couple of weeks. Raul
Synchronization issues in JDEbug
Hello, It looks like JDEbug needs to have some methods synchronized. I tried setting a breakpoint while the process was running, and got the following in the Message window: Setting breakpoint at line 85 in d:/jaguar_te1.2/KBR_ISD_VOB/Jaguar_Plan_Generator_Component/source/PhysicalNetworkBuilder/com/alphatech/kbr/jaguar/networkbuilder/SpatialSpec.java. Error: evaluating debugger output caused a Lisp error. See *messages* buffer for details. Error: evaluating output from the debugger caused a Lisp error. Debugger output: it.framework.TestSuite TestSuite.java 208 runTest) (list 25 junit.framework.TestSuite TestSuite.java 203 run). Lisp error: (void-variable it.framework.TestSuite) Breakpoint set at line 85 in class d:/jaguar_te1.2/KBR_ISD_VOB/Jaguar_Plan_Generator_Component/source/PhysicalNetworkBuilder/com/alphatech/kbr/jaguar/networkbuilder/SpatialSpec.java. It also appears that, at least with JDK 1.4.2, there is a lot of useless traffic going from Java to emacs. My *JDEBug* buffer is full of output that looks like (jde-dbo-event-set 1 none (list Thread 1 main runnable suspended by debugger (list stack traces of several threads ))) Since jde-dbo-event-set is a no-op if the optional fourth arg is omitted, this slows down the debugger considerably. If the java side checked for the fourth argument, is could avoid a lot of toString calls, bandwidth to Emacs and parsing of the string by Emacs. Troy Troy Daniels [EMAIL PROTECTED] 781-273-3388 x218
Re: jde and emacs memory usage
That's cool... but it's still only about one megabyte. I still have close to 100 megabytes of unexplained memory somewhere... any thoughts? Raul On Thu, 2004-11-18 at 13:15 -0800, Suraj Acharya wrote: The jde-beanshell-buffer is something that jde-usages to record the output of bsh. It's like a *Messages* buffer for the beanshell, but unlike *Messages* it doesn't clear out old entries. Adding the equivalent of message-log-size for this buffer is on my to-do list. You can delete the buffer at any point without any adverse effects. The next time jde-usages makes a call to bsh it will create the buffer if it does not exist. Suraj On Thu, 18 Nov 2004 11:53:11 -0800, Raul Acevedo [EMAIL PROTECTED] wrote: Right now my Emacs process is using 127 Megs of memory. While the *jde-beanshell-scratch* buffer size is 1239491, and another buffer I have is also just over 1 Meg, the total sum of all my buffers is still only a few megabytes, I definitely am not consuming anywhere near 100 megabytes in buffers. What could be taking up all the memory? How do I free it up? I've had emacs run out of memory a few times in the last couple of weeks. Raul
Re[1]: jde and emacs memory usage
Hi, Here is something fun to try: M-x load-library RET chart RET M-x chart-emacs-storage RET It is possible that semantic's tag caches are filling up all your space. Check the size of your semanticdb.cache files for a vague clue of how much string space is being used by semantic. Eric Raul Acevedo [EMAIL PROTECTED] seems to think that: Right now my Emacs process is using 127 Megs of memory. While the *jde-beanshell-scratch* buffer size is 1239491, and another buffer I have is also just over 1 Meg, the total sum of all my buffers is still only a few megabytes, I definitely am not consuming anywhere near 100 megabytes in buffers. What could be taking up all the memory? How do I free it up? I've had emacs run out of memory a few times in the last couple of weeks. Raul -- Eric Ludlam: [EMAIL PROTECTED], [EMAIL PROTECTED] Home: http://www.ludlam.netSiege: www.siege-engine.com Emacs: http://cedet.sourceforge.net GNU: www.gnu.org
Re[3]: jde and emacs memory usage
Raul Acevedo [EMAIL PROTECTED] seems to think that: Wow, that chart thing is pretty cool. :) There are several random chart functions, plus a chart menu item in the Senator menu. It shows strings/2 as taking up 31 Meg, which I assume means 62 Megs and it shows it as strings/2 so the chart can be shown on a single buffer when the next biggest item is conses at only 1 Meg. I have 33 Java buffers averaging 10k each... so that's about 33 Meg, plus 62 Meg for strings, adds up to 100 Meg right there. Why so many strings? Most semantic.cache files are 50k, the biggest one I found is 150k. You might have some very large hidden buffers. Hidden buffers start with a space character. Probably your best task is just to get some sort of active monitor up watching Emacs and see what you do that makes it grow very large. Eric Raul On Thu, 2004-11-18 at 17:46 -0500, Eric M. Ludlam wrote: Hi, Here is something fun to try: M-x load-library RET chart RET M-x chart-emacs-storage RET It is possible that semantic's tag caches are filling up all your space. Check the size of your semanticdb.cache files for a vague clue of how much string space is being used by semantic. Eric Raul Acevedo [EMAIL PROTECTED] seems to think that: Right now my Emacs process is using 127 Megs of memory. While the *jde-beanshell-scratch* buffer size is 1239491, and another buffer I have is also just over 1 Meg, the total sum of all my buffers is still only a few megabytes, I definitely am not consuming anywhere near 100 megabytes in buffers. What could be taking up all the memory? How do I free it up? I've had emacs run out of memory a few times in the last couple of weeks. Raul
Re: Problems debugging files with more than 1000 lines.
tor, 2004-11-18 kl. 08:23 skrev Morten / Datagruppen MultiMED: ons, 2004-11-17 kl. 22:21 skrev Javier S. Lopez: Morten [EMAIL PROTECTED] writes: ons, 2004-11-17 kl. 14:05 skrev Javier S. Lopez: This has been fixed since version 2.3.4beta4 cut cut Not sure what to to tell you. Is is possible that the old version is getting loaded somehow. I would be rather surprised if that was the case. When I click the jde menu, and hold the mouse over help, it displays jde 2.3.4. Is there another way of testing which version of JDE I am running? It seems strange that I get the error that has been fixed ... Morten .
