Hi,
I have previously tried to track that error down and I came up with a
way of reproducing the error:

class TestClass {
    private boolean aSomeFlag;

    boolean isEnabled() {
        return aSomeFlag;
    }
}

If you delete the parentheses of the isEnabled method, then wait for the
automatic reparse done by semantic, then delete the next two characters
without semantic doing reparse in between, the error occurs.

File when error occurs:

class TestClass {
    private boolean aSomeFlag;
 
    boolean isEnabl {
         return aSomeFlag;
    }
}


However, since upgrading semantic to the latest version 14 (no beta) I
have not been able to reproduce this error. I think that Eric Ludlam may
have
been mingling with the auto-parse features of semantic since the spontaneous
C-l behaviour previously mentionened on the JDEE mailing list also seems to
have disappeared. . The two 'features' may somehow have been interrelated
since
they apparently both appeared in connection with some reparse.

Hence my advise is to upgrade to the lastest version of semantic.

/Morten

-----Original Message-----
From: mark a foltz [mailto:[EMAIL PROTECTED]]
Sent: 7. august 2002 19:00
To: [EMAIL PROTECTED]; [EMAIL PROTECTED]
Subject: semantic error


hello,

while editing files in jde, occasionally the font-lock dies and a "stack 
overflow in equals" error is reported in the message buffer.  this seems 
to happen when editing method bodies, but it's hard to tell.  in this 
case i was doing a search-replace and the replace target was in a method 
body.

i applied the patch posted earlier in this list to semantic-imenu.el to 
try and fix the problem, but no avail.  david ponce's overlay-fix.el 
also doesn't apply since i'm using emacs 21.

emacs: 21.2.1
jde: 2.2.9beta10
semantic: 1.4beta14
speedbar: 0.14beta3
eieio: 0.17beta4

backtrace and .emacs are attached.
i can send the code snippet too if that helps.

best,
m.

-- 
mark a foltz -*- mit ai lab -*- [EMAIL PROTECTED] -*- 617.253.8926

Reply via email to