KMail is still failing for me, but Backtrace has started reporting stuff, as follows: (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...[New Thread 1024 (LWP 1762)] (no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... 0x413b5099 in wait4 () from /lib/libc.so.6 #0 0x413b5099 in wait4 () from /lib/libc.so.6 #1 0x4142fbd8 in __DTOR_END__ () from /lib/libc.so.6 #2 0x4128d072 in waitpid () from /lib/libpthread.so.0 #3 0x40a350de in KCrash::defaultCrashHandler () from /opt/kde3/lib/libkdecore.so.4 #4 0x4128aa74 in pthread_sighandler () from /lib/libpthread.so.0 #5 <signal handler called> #6 0x0811a539 in KDialog::marginHint () #7 0x084ed820 in ?? () #8 0x08128cb0 in KDialog::marginHint () #9 0x08128d10 in KDialog::marginHint () #10 0x08128d10 in KDialog::marginHint () #11 0x08128d10 in KDialog::marginHint () #12 0x08128d10 in KDialog::marginHint () #13 0x08119abb in KDialog::marginHint () #14 0x081a05a4 in KDialog::marginHint () #15 0x081a4334 in KDialog::marginHint () #16 0x4132a9ed in __libc_start_main () from /lib/libc.so.6 I have not tried every other application on my system, but those that I have been using don't seem to be broken... Anybody interpret what's wrong, here? Or, is there a HowTo or a website that can tell me how to interpret the above output? Meanwhile, I have done the following: - created another user on my system -- KMail starts for that user, but of course does nothing because the user doesn't have a mail account on our company server... still, the program starts with no reported error - moved my own /home/kmclauchlan/Mail directory and it's subdirectories to a temp directory - tried starting KMail again -- no change - copied the virgin, empty /Mail directory structure from the "Otherguy" user into my home directory started KMail and it failed as usual with SIGSEGV before opening Previously, I had reported re-installing the knetwork package, which is purported to contain KMail. That had no effect. I'm baffled as to where to look. Why would ONE program be segfaulting? How do you trace to see what it wants, that it's not getting? I didn't see any log files in /var/log that seemed to be KDE-related. Does anybody know a good HowTo on "debugging Kommercial apps for Dummies" ?? Is anybody using directories with KMail, rather than MBOX? I was told, last year that this was preferable due to the server I'm connected to. I don't recall the reasoning. /kevin (now with 2520 messages in his Outlook inbox cuz he won't let Outlook "delete viewed messages from server" before he can get Linux mail working again... Mygawd it's ugly! :-)
On Sat, 16 Nov 2002 09:34 am, KMcLauchlan@chrysalis-its.com wrote:
KMail is still failing for me, but Backtrace has started reporting stuff, as follows:
Kevin, Sounds like something is corrupted in your kde settings. Have you tried renaming the ~/.kde directory to say ~/.kde.old and deleting all references to KDE in /tmp which belongs to you and any MCOP files in your home directory. Log out of KDE and relog in. This will recreate all the KDE files again. Remember you will have to reconfigure KDE again if you do this although all the settings will be in the ~/.kde.old subdirectory. Regards, Graham Smith ---------------------------------------------------------
On 11/16/2002 06:34 AM, KMcLauchlan@chrysalis-its.com wrote:
KMail is still failing for me, but Backtrace has started reporting stuff, as follows:
I don't know if this will help, but it is worth a try. I just installed the newest kdelibs3 (in hopes that maybe all the 'bugs' were worked out in this one, but again my kedit crashes [it seems that kedit, kdevelop, and kmail segfaulting were related to the update to 3.0.4 for several of us]. I know it worked for Anders before, and at work as well, so I decided to try a bit more. One thing I noticed is the looks of the desktop looked somehow different. I decided to check qt stuff, since the new kdelibs3 requires the latest qt3-3.0.5. One thing I read here on the list was the double entry of the path, so I fired up the qt config app, deleted a duplicate entry, but while I was there, I noticed there was some king of theme styler or something. I changed it from unknown to CDE, then Platinum, and Kedit worked without crashing (so far). It was consistent before so it appears this may be a key. I also noticed then going through the Control Center that the same qt app is in there (i.e. integrated), so maybe this is the change. Also, my desktop font was wrong. Anyway, HTH. Maybe the theme of the build machine affected the binary? -- Joe & Sesil Morris New Tribes Mission Email Address: Joe_Morris@ntm.org Web Address: http://www.mydestiny.net/~joe_morris Registered Linux user 231871 God said, I AM that I AM. I say, by the grace of God, I am what I am.
participants (3)
-
Graham Smith -
Joe Morris (NTM) -
KMcLauchlan＠chrysalis-its.com