Petter M�hl�n <[EMAIL PROTECTED]> writes: > The exception is throw by the Java side of JDEbug. It keeps a map of object > id (269 in this case) and object reference in the process being debugged. > The exception indicates that it cannot find the object with reference 269. I > haven't looked at the 2.3.3 code, but if I remember right, in previous > versions, JDEbug never cleaned out the object store. I would say that the > most likely sources of the problem are: > > - the elisp side of JDEbug is using an invalid object ID (due to a bug), or > - the Java side of JDEbug is nowadays cleaning out the object store, and the > object in question has been cleaned out from the Java side but not the elisp > side (meaning there is some bug in the cleaning out of objects). > > More questions in addition to what Andrew asked: does this happen > immediately and always for the same object? Or do you have to run the > debugger for some time first? Does it matter which program you are > debugging?
It happens for all objects in every small test contexts. The debug window 'JDEbug 1' appears on the left side - unfortunatly only under Linux with a width of zero. In the JDEbug 1 window the values look fine. I did this test in a test scenario with 'emacs -q'. Ok, I am now seeing that this feature is maybe now not so important because looking to the JDEbug 1 window is more convenient. How can I recompile the java files because I want to fix the width problem? I do not found any build or make file. Harald
