Sebastian Guttenberg wrote: > Below are the last messages of gdb. The interrupt signal came from me > pressing ctrl-c in gdb, because lyx did not crash, just freezed. After > that you see the backtrace. Hope this is enough to give somebody an idea > what goes wrong. Otherwise tell me what information you need.
few things can be improved: 1. there are not visible line numbers and variables. this can be solved by setting debugging symbols on. (--enable-debug or something like this in configure). 2. in case of freeze, it would be better to get more backtraces to get idea where is the infinite loop. like in the following recipy: ctrl+c bt cont ctrl+c bt the second backtrace will probably give you different last few entries which helps to detect from which function we are not able to escape. if you are going hard after this bug, then feel free to file a new bug and put more backtraces and diagnostics there. pavel
