Hi, I did a little debugging and tracked the crash down to this: In 'jde-expand-classpath if jde-expand-classpath-p!=nil JDE passes the huge classpath I'm having to XEmacs' 'file-exists-p function which then causes the crash.
Now I'm not sure if this is wanted behaviour to pass all of the classpath to the 'file-exists-p function or not. Anyway, as a workaround I set jde-expand-classpath-p to nil and JDE works again (for me) ;-) Cheers, Christian Schmitt > -----Ursprungliche Nachricht----- > Von: Christian Schmitt [mailto:[EMAIL PROTECTED] > Gesendet: Mittwoch, 19. Marz 2003 09:31 > An: [EMAIL PROTECTED] > Cc: [EMAIL PROTECTED] > Betreff: jde-global-classpath too long?! > > > > Please enter the details of your bug report here > > In our project the jar files moved one folder down in the file > system. Since then XEmacs crashes whenever I try to do anything that > involves usage of the classpath, i.e. opening a BSH buffer or doing > JavaDoc generation. Also typing C-c C-v C-y crashes XEmacs big time. > I'm suspecting it's got something to do with the length of the > jde-global-classpath variable. When I shorten it to only one or two > jar files JDE works OK. > I'm sorry that I can't include a stacktrace, but when XEmacs crashes > it opens a console window starts to type something and then it closes > again before I have a chance to copy the contents. > > Thanks for your time and help. > > Christian Schmitt > > <Lot's of system info deleted/>
