AFAIK version XX.Y where Y is > 1 are molstly bug fix releases with only a few new features...all the new stuff is mostly in the .1 version so it's obviously that there can be guggs which have a good chance to be fixed in a .2, .3 or .4 version - so IMHO builing and using 22.3 instead of 22.1 is worth a try and probbaly also worth the effort....
I'm not a linux-guy but AFAIK builing an emacs is not rerally hard because Linux has all on board what is necessary - often calling ./configure & make is enough ;-)
Von: Laurynas Biveinis [mailto:laurynas.biveinis@...]
Gesendet: Dienstag, 23. Juni 2009 17:09
An: Berndl, Klaus
Cc: eric@...; cedet-semantic@...
Betreff: Re: [cedet-semantic] CEDET hangs Emacs?
Because I'm not 100% positive that this is indeed a bug in 22.1. This Emacs version is packaged in Ubuntu 8.04 LTS, to upgrade I'd have to build it myself, which I'd like to avoid if possible.
> Why do you not use Emacs 22.2 or greater if there is no problem?
> Why instisting in Ewmacs 22.1 - just use the current official release 22.3!
> -----Ursprüngliche Nachricht-----
> Von: Laurynas Biveinis [mailto:laurynas.biveinis@...]
> Gesendet: Dienstag, 23. Juni 2009 16:32
> An: eric@...
> Cc: cedet-semantic@...
> Betreff: Re: [cedet-semantic] CEDET hangs Emacs?
> Thanks for your suggestions. My replies are below.
>> All the idle hooks in CEDET allow C-g to get through, so you can use
>> M-x toggle-debug-on-quit RET
>> and then C-g should show a useful stack trace.
> Uhm, it doesn't. I do M-x toggle-debug-on-quit, then proceed to visit a .c file, then after the buffer contents become thrashed, C-g still drops me into shell. No stacktrace. It goes like this:
> lauris@...:~$ emacs -nw
> C-g here -----> + Stopped emacs -nw lauris@...:~$
> fg emacs -nw Auto-save? (y or n) y Auto-save done Abort (and dump
> core)? (y or n) y Fatal error (6)^[OA^[OB^[OAAborted
> If I choose not to abort, then I get "Continuing..." on console and nothing else happens.
>> Alternately, if you find a place that has this slowdown, you can do
>> put a cursor there, and use:
>> M-x semantic-debug-idle-function RET
>> M-x semantic-debug-idle-work-function RET
>> to force those idle features to run with various debug flags turned on.
> There is no local place in the file which has a slowdown. I can keep the cursor inside the comment block, for example, with same results.
>> Once you get a stack with toggle-debug-on-quit in one of these
>> situations, if you read the stack, you will likely see the name of
>> one of the idle features there. You can then turn it off to revive
>> the speed you would like.
> I think it's not about speed, it's about not hanging/crashing emacs :) I use the same CEDET version with same codebase under Emacs 22.2 (the problems I describe here are on 22.1) and slowdown because of parsing the source code is noticeable but nothing like this.
>> Since you are using a particularly large code base, and it is plain
>> C, you can probably use GNU Global and the CEDET features it uses to
>> get good performance looking up symbols with minimal CEDET configuration.
> Yes, I am planning to try GNU Global
>> It may also be you just need to let the idle process run to
>> completion sometime. ie, just let it sit for a while, and when it is
>> done, all the symbols will be saved away for later use, and it may not do it again.
> Again, with Emacs 22.2 the idle process runs to completion quite fast.
> So, all in all, I'm puzzled. I don't think that I am experiencing just
> a slowdown due to parsing, but rather something bad in CEDET/Emacs
> 22.1 interaction, maybe some Emacs core bug, which was present in 22.1 but was fixed in 22.2?
> Thanks again,
> -------- Are you an open source citizen? Join us for the Open Source
> Bridge conference!
> Portland, OR, June 17-19. Two days of sessions, one day of unconference: $250.
> Need another reason to go? 24-hour hacker lounge. Register today!
> idge.org _______________________________________________
> cedet-semantic mailing list