Am Donnerstag, 17. August 2006 18:27 schrieb Rudi Gaelzer: > Jean-Marc, > I don't think this is possible. I mean, the crash seems to occur at any > instant. I can not identify any particular sequence of keystrokes that will > ignite it... the only pattern I can see is that the window crashes always > after a lot of intensive editing in mathed mode, usually when I'm leaving or > entering a math environment.
Did you compile LyX yourself? If yes, it would be nice if you could compile it with debugging symbols (run configure with --enable-debug). Then run LyX in gdb, and when it crashes press bt for a backtrace and send that. That might give us useful information. > I could send the bug report obtained from "lyx -dbg any 2> lyx_bug.txt", as > Michael Abshoff suggested, but the file, even when compressed with bzip2, is > above the 60000b limit of the mailer-deamon. You could try lyx -dbg mathed,action 2> lyx_bug.txt instead. If that is still too big then simply send the last 1000 lines. > Should I create a bug report at bugzilla? You can, but it does not help much if the bug is not reproducible and we don't have a backtrace and/or debug output. If you manage to get a backtrace or debug output please do. The strange thing is that heavy math editing works rather well for me in 1.4.3svn. What OS/distribution and what compiler do you use? We have reported crashes with gcc 4.1 that might be related to this, see e.g. http://bugzilla.lyx.org/show_bug.cgi?id=2677 Georg
