On Saturday 28 April 2007 07:03:58 Michael Nottebrock wrote: > On Friday, 27. April 2007, David Southwell wrote: > > I am sorry to say that it does not entirely work. The crashes are much > > more infrequent -- gone for over 24 hours without a crash of kmail - that > > compares with crashes every 3 or 4 hours previously. Also it did not > > totally freeze the whole screen or require a ctrl>alt>backspace to get > > out of the problem but I did have to log out of the kde session. > > > > Is there anything I can do to help trace the cause. > > Recompile the kdepim3 port like this: > > cd /usr/ports/deskutils/kdepim3 > make -DWANT_KDE_DEBUG > make deinstall install > > Make sure your terminal history buffer is sufficiently big. If you're using > konsole, I recommend you select "Clear History" from the Edit menu, > then "History..." from the Settings menu and click "Set Unlimited" and Ok > at this point. Then start kmail (or kontact) in the debugger: > > gdb kmail > > Eventually the gdb prompt will appear. Type the following then: > set args --nofork > > Then type: > run > > Now kmail should start as usual. Use it until a crash/hang of kmail occurs. > Do not log out of KDE and get the shell window in which you started the > debugger with kmail running in it and check if the gdb prompt is visible - > if it isn't, hit CTRL-C, which should bring it up. Once you get the prompt, > type: > > info threads > > You will get some output like this: > > 6 Thread 5 (sleeping) 0x29f7c233 in foobar () from /usr/lib/libfoo.so.1 > 5 Thread 4 (sleeping) 0x29f7c233 in foobar () from /usr/lib/libfoo.so.1 > 4 Thread 3 (sleeping) 0x29f7c233 in foobar () from /usr/lib/libfoo.so.1 > 3 Thread 2 (sleeping) 0x29f7c233 in foobar () from /usr/lib/libfoo.so.1 > 2 Thread 1 (sleeping) 0x29f7c233 in foobar () from /usr/lib/libfoo.so.1 > > Now select a thread: > > thread 6 > > And get a stack trace of it: > > bt > > Do this for each thread in the list. Then save the complete terminal buffer > (in Konsole, use "Save History As" in the Edit menu) to a file and send the > output here (or open a bug report on bugs.kde.org with that file attached > and report the number it gets assigned here on the list). > > > Good luck, Thank you Michael
Well after a major interuption in my life dealing with some health issues I got round to following your suggestions. The result is a PR 114066 and a new thread entiled ports/114066: Kmail crashes. Thank you Michael for your ever helpful guidance david _______________________________________________ kde-freebsd mailing list kde-freebsd@kde.org https://mail.kde.org/mailman/listinfo/kde-freebsd