Re: jde-2.3.3 error by jde-bug-evaluate-expression
Does it ask for an expression to evaluate first? Harald Maier [EMAIL PROTECTED] writes: Hello all, I installed jde-2.3.3 with eieio-0.17 elib-1.0 semantic-1.4.4 speedbar-0.14beta4 When I evaluate 'jde-bug-evaluate-expression' in a JDEbug session I get the following error: , | Error: cannot get object 269. | Reason: Exception during command execution: jde.debugger.JDEException: No such object exists. | eieio-oref: Wrong type argument: (or object-p class-p), nil ` jde-2.3.2 works fine on this operation. Is this a known bug or it it related to a configuration problem? Harald
Re: jde-2.3.3 error by jde-bug-evaluate-expression
Andrew Hyatt [EMAIL PROTECTED] writes: Does it ask for an expression to evaluate first? Yes, it asks for an expression and afterwards the above error is signaled. When I evaluate 'jde-bug-evaluate-expression' in a JDEbug session I get the following error: , | Error: cannot get object 269. | Reason: Exception during command execution: jde.debugger.JDEException: No such object exists. | eieio-oref: Wrong type argument: (or object-p class-p), nil ` Harald
Re: jde-2.3.3 error by jde-bug-evaluate-expression
What sort of thing are you trying to evaluate? Perhaps the bug is that the evaluation returns null (legitimately, perhaps) and throws an error incorrectly? Or perhaps a variable has gone out of scope and you are trying to evaluate it? Harald Maier [EMAIL PROTECTED] writes: Andrew Hyatt [EMAIL PROTECTED] writes: Does it ask for an expression to evaluate first? Yes, it asks for an expression and afterwards the above error is signaled. When I evaluate 'jde-bug-evaluate-expression' in a JDEbug session I get the following error: , | Error: cannot get object 269. | Reason: Exception during command execution: jde.debugger.JDEException: No such object exists. | eieio-oref: Wrong type argument: (or object-p class-p), nil ` Harald
RE: jde-2.3.3 error by jde-bug-evaluate-expression
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? / Petter -Original Message- From: Andrew Hyatt [mailto:[EMAIL PROTECTED] Sent: den 26 januari 2004 19:32 To: Harald Maier Cc: Andrew Hyatt; [EMAIL PROTECTED] Subject: Re: jde-2.3.3 error by jde-bug-evaluate-expression What sort of thing are you trying to evaluate? Perhaps the bug is that the evaluation returns null (legitimately, perhaps) and throws an error incorrectly? Or perhaps a variable has gone out of scope and you are trying to evaluate it? Harald Maier [EMAIL PROTECTED] writes: Andrew Hyatt [EMAIL PROTECTED] writes: Does it ask for an expression to evaluate first? Yes, it asks for an expression and afterwards the above error is signaled. When I evaluate 'jde-bug-evaluate-expression' in a JDEbug session I get the following error: , | Error: cannot get object 269. | Reason: Exception during command execution: jde.debugger.JDEException: No such object exists. | eieio-oref: Wrong type argument: (or object-p class-p), nil ` Harald
