Darren Freeman wrote: > > I should learn to use GDB one day =) But usually the odd printf() gets > me out of trouble...
It's really not at all that difficult. You're just afraid of typing "gdb" at your prompt :). Suppose you compile CVS in your LyX CVS-root directory. You then have the executable as src/lyx (right?). Simply type "gdb src/lyx". You'll get some gdb info messages and the gdb prompt "(gdb)". Without arguments to lyx, you simply type here "run". If lyx needed commandline arguments, you'll do first "set args arg1 arg2 arg3", for examples "set args mylyxfile.lyx". Then type "run" after that. The "run" will start the executable (with the arguments, if you did "set args"). Do what you want to do in LyX to generate the crash. As soon as the crash happens, gdb will stop the executable, tell you what signal has been delivered and gives you the gdb prompt again "(gdb)". Then type "bt" or "backtrace", which gives the full information of what has led to the crash. Send all that to the list and hopefully someone can make sense of it. Gdb is really very, very simple to use! >>Darren, I vaguely seem to remember that you are also running on FreeBSD. Is that so? >>Would that make this a typical FreeBSD thing, if Andre and others do not see this? > > No, I run Mandrake Linux 9.0 on an Athlon. Good, so this is not an odd FreeBSD behaviour, but a general bug. Regards, Rob.
