KMuddy

Kmuddy Help Help     Search Search     Members Members

Welcome! ( Recent posts | Mark all | Login | Register ) » KMuddy Discussion Forums » KMuddy » Bug Reports » 0.8pre5 crash

< Newer Topic :: Older Topic >
New Poll
New Topic
Reply
Pages: << prev 1 next >>
0.8pre5 crash
 
This member is currently offline taulibrus
Member

Avatar

Member Level

Group: Members
Posts: 12
Joined: Jul 10, 2006
Go to the bottom of the page Go to the top of the page
Quote
Posted Jul 10, 2006, 6:31 pm   
I got the 0.8pre5 version to compile OK but when I started it from kmenu the KDE crash handler popped up with the following message:

The application Kmuddy (kmuddy) crashed and caused the signal 11 (SIGSEGV).

Here's the backtrace:
Code:
Using host libthread_db library "/lib/tls/libthread_db.so.1".
`system-supplied DSO at 0xffffe000' has disappeared; keeping its symbols.
[Thread debugging using libthread_db enabled]
[New Thread 1102729280 (LWP 7147)]
[KCrash handler]
#4  0x40644bcf in KMainWindow::initKMainWindow ()
   from /opt/kde3/lib/libkdeui.so.4
#5  0x406dd892 in KMainWindow::KMainWindow () from /opt/kde3/lib/libkdeui.so.4
#6  0x08075b51 in KMuddy::KMuddy ()
#7  0x0807e027 in main ()


BTW I'm running SuSE 10.0

Thanks.
.........................
There are 10 kinds of people,
those who can read binary and those who can't.
AIM
PM
This member is currently offline Mecir
KMuddy Author

Member Level

Group: Administrators
Posts: 1,586
Joined: Feb 2, 2003
Go to the bottom of the page Go to the top of the page
Quote
Posted Jul 11, 2006, 12:16 am   
Hmm, this doesn't really tell me anything. Try running it with gdb ?
SuSE 10.0 here too, and no crashes.
.........................
/ Tomas
PM
This member is currently offline taulibrus
Member

Avatar

Member Level

Group: Members
Posts: 12
Joined: Jul 10, 2006
Go to the bottom of the page Go to the top of the page
Quote
Posted Jul 11, 2006, 6:50 am   Last edited Jul 11, 2006, 6:57 am by taulibrus
I'm sorry.  I'm almost as new to linux as I am to mudding. 

Could I have missed something in the compile?  I'm pretty sure I got all the kde and qt devel packages. And, I compiled the MXP libs.

The 0.7.1 version compiled and runs great.

I was going to ask you what 'gdb' is, but google saved me from my ignorance.  I'll try it and get back to you.  Be nice to me, I'm almost as new to linux as I am to mudding.

Thanks.
.........................
There are 10 kinds of people,
those who can read binary and those who can't.
AIM
PM
This member is currently offline Mecir
KMuddy Author

Member Level

Group: Administrators
Posts: 1,586
Joined: Feb 2, 2003
Go to the bottom of the page Go to the top of the page
Quote
Posted Jul 12, 2006, 12:31 am   
-grin- sure, no worries, we were all starting one day or the other :)

The ideal way to get a good-enough backtrace is as follows:

- get the tarball, cd to directory where it's located
tar xzf kmuddy-0.8pre5.tar.gz
cd kmuddy-0.8pre5
./configure --enable-debug
make
su
(enter root password)
make install
exit
gdb kmuddy
r
(wait for it to crash)
bt
(keep pressing enter while there's more data)
(copy/paste the full backtrace)

.........................
/ Tomas
PM
This member is currently offline taulibrus
Member

Avatar

Member Level

Group: Members
Posts: 12
Joined: Jul 10, 2006
Go to the bottom of the page Go to the top of the page
Quote
Posted Jul 12, 2006, 6:21 am   
OK, great. Thanks. That will be tremendously useful if I have another crash.

This one seems to have fixed itself, though.  When I re-booted my system there was a glitch with my wlan0 config.  After re-setting that and bumping the router I got SuSE to boot up clean.  Then I launched kmuddy from the kmenu icon and it runs great. Woot!
.........................
There are 10 kinds of people,
those who can read binary and those who can't.
AIM
PM
This member is currently offline Mecir
KMuddy Author

Member Level

Group: Administrators
Posts: 1,586
Joined: Feb 2, 2003
Go to the bottom of the page Go to the top of the page
Quote
Posted Jul 13, 2006, 12:38 am   
Ah, you were likely trying to run it too quickly, before KDE updated all its databases. Or something of the sort.
.........................
/ Tomas
PM
This member is currently offline taulibrus
Member

Avatar

Member Level

Group: Members
Posts: 12
Joined: Jul 10, 2006
Go to the bottom of the page Go to the top of the page
Quote
Posted Jul 23, 2006, 2:30 pm   
OK, it's happening again.  0.7.1 runs fne but 0.8pre5 crashes on startup.

Here's the trace from gdb:
Code:
pc81:/home/tomr/kmuddy-0.8pre5 # gdb kmuddy
GNU gdb 6.3
Copyright 2004 Free Software Foundation, Inc.
GDB is free software, covered by the GNU General Public License, and you are
welcome to change it and/or distribute copies of it under certain conditions.
Type "show copying" to see the conditions.
There is absolutely no warranty for GDB.  Type "show warranty" for details.
This GDB was configured as "i586-suse-linux"...Using host libthread_db library "
/lib/tls/libthread_db.so.1".

(gdb) r
Starting program: /opt/kde3/bin/kmuddy
[Thread debugging using libthread_db enabled]
[New Thread 1102729280 (LWP 13295)]
Creating link /root/.kde/socket-pc81.
Created link from "/root/.kde/socket-pc81" to "/tmp/ksocket-root"
/usr/X11R6/bin/iceauth:  creating new authority file /root/.ICEauthority
Creating link /root/.kde/tmp-pc81.
Created link from "/root/.kde/tmp-pc81" to "/tmp/kde-root"
kbuildsycoca running...
Creating link /root/.kde/cache-pc81.
Created link from "/root/.kde/cache-pc81" to "/var/tmp/kdecache-root"
Reusing existing ksycoca
Invalid entry (missing '=') at /tmp/kde-root/kconf_updateI3rV6b.tmp:1

Program received signal SIGSEGV, Segmentation fault.
[Switching to Thread 1102729280 (LWP 13295)]
0x00000000 in ?? ()
(gdb) bt
#0  0x00000000 in ?? ()
#1  0x40644bdb in KMainWindow::initKMainWindow ()
   from /opt/kde3/lib/libkdeui.so.4
#2  0x406dd892 in KMainWindow::KMainWindow () from /opt/kde3/lib/libkdeui.so.4
#3  0x08075b51 in KMuddy::KMuddy ()
#4  0x0807e027 in main ()
(gdb)


With my untrained eye it looks like a fault in kde rather kmuddy.  What do you think?
.........................
There are 10 kinds of people,
those who can read binary and those who can't.
AIM
PM
This member is currently offline Mecir
KMuddy Author

Member Level

Group: Administrators
Posts: 1,586
Joined: Feb 2, 2003
Go to the bottom of the page Go to the top of the page
Quote
Posted Jul 24, 2006, 12:37 am   
Hmm, you seem to be running it as a root, which may be a problem, as KDE is started under a regular user, and running an app as root makes it create new databases and whatnot - pretty much simulating the situation when you ran it for the first time.
.........................
/ Tomas
PM
This member is currently offline taulibrus
Member

Avatar

Member Level

Group: Members
Posts: 12
Joined: Jul 10, 2006
Go to the bottom of the page Go to the top of the page
Quote
Posted Jul 24, 2006, 7:35 am   
Whoops!  Duh! *slaps forehead*

So, I should have switched back to my user account before running gdb?  OK.  I'll give it a whirl and see what happens.
.........................
There are 10 kinds of people,
those who can read binary and those who can't.
AIM
PM
This member is currently offline taulibrus
Member

Avatar

Member Level

Group: Members
Posts: 12
Joined: Jul 10, 2006
Go to the bottom of the page Go to the top of the page
Quote
Posted Jul 25, 2006, 6:06 pm   
I still  can't get 0.8pre5 to run.  Here's the trace from gdb
Code:
tomr@pc81:~/kmuddy-0.8pre5> gdb kmuddy
GNU gdb 6.3
Copyright 2004 Free Software Foundation, Inc.
GDB is free software, covered by the GNU General Public License, and you are
welcome to change it and/or distribute copies of it under certain conditions.
Type "show copying" to see the conditions.
There is absolutely no warranty for GDB.  Type "show warranty" for details.
This GDB was configured as "i586-suse-linux"...Using host libthread_db library "/lib/tls/libthread_db.so.1".

(gdb) r
Starting program: /opt/kde3/bin/kmuddy
[Thread debugging using libthread_db enabled]
[New Thread 1102729280 (LWP 19815)]

Program received signal SIGSEGV, Segmentation fault.
[Switching to Thread 1102729280 (LWP 19815)]
0x40644bcf in KMainWindow::initKMainWindow () from /opt/kde3/lib/libkdeui.so.4
(gdb) bt
#0  0x40644bcf in KMainWindow::initKMainWindow ()
   from /opt/kde3/lib/libkdeui.so.4
#1  0x406dd892 in KMainWindow::KMainWindow () from /opt/kde3/lib/libkdeui.so.4
#2  0x08075b51 in KMuddy::KMuddy ()
#3  0x0807e027 in main ()
(gdb)
.........................
There are 10 kinds of people,
those who can read binary and those who can't.
AIM
PM
This member is currently offline taulibrus
Member

Avatar

Member Level

Group: Members
Posts: 12
Joined: Jul 10, 2006
Go to the bottom of the page Go to the top of the page
Quote
Posted Jul 25, 2006, 7:15 pm   Last edited Jul 25, 2006, 7:16 pm by taulibrus
OK, quick update.

I got it to run.  Yippee!

I ran
make clean
rm /opt/kde3/bin/kmuddy

then recompiled with
make
make install. 

Now it runs.
.........................
There are 10 kinds of people,
those who can read binary and those who can't.
AIM
PM
This member is currently offline Mecir
KMuddy Author

Member Level

Group: Administrators
Posts: 1,586
Joined: Feb 2, 2003
Go to the bottom of the page Go to the top of the page
Quote
Posted Jul 26, 2006, 12:29 am   
Excellent !
.........................
/ Tomas
PM
» KMuddy Discussion Forums » KMuddy » Bug Reports » 0.8pre5 crash
 
New Poll
New Topic
Reply
Pages:<< prev 1 next >>

Powered by Quicksilver Forums © 2005-2007 The Quicksilver Forums Development Team
Based on MercuryBoard © 2001-2005 The Mercury Development Team
IBFBlue skin by Samson. Adapted from Invisionboard 1.31f

Valid XHTML 1.1! Valid CSS!

Sep 9, 2010, 9:08 pm