gmonfort
New Member
Group: Members
Posts: 5
Joined: Jan 14, 2007
|
|
Posted Jan 14, 2007, 8:33 pm Last edited Apr 11, 2008, 2:52 pm by Samson
|
First of all would like to congratulate Thomas Mecir && his team for their astonishing work with kmuddy.
I am kind of new to linux and also to kmuddy, of course, I moved about a couple months ago && I'm totally satisfied.
My background is MS && Zmud, but I can tell you that I feel really confortable with my debian machine && kmuddy as well.
Ok, that said, now lets go straight to what I have found in about 45 days of kmuddy use:
Sometimes, while playing, entering the word "eq" && hitting the <return> key I get the following message from KDE:
"The application KMuddy crashed and caused the signal 11 (SIGSEGV)"
then the application obviously closes.
Browsing this forum I found that this happened to someone else before, more or less the same,
http://www.kmuddy.com/mercuryboard/index.php?a=topic&t=1093'
but unfortunelly the solution provided didn't work for me.
This a very weird thing, sometimes I can reproduce the error but not always && I have used kmuddy for more than 6 hours straight without any symptoms. Entire weeks playing smoothly until one day I send the "eq" command && suddenly kmuddy crashes ...
Needless to say that I typed that command before, at least dozens of times, without any problems but it's always the very same command.
I tryed avoiding the short form of this command 'eq', entering the full word 'equipo', 'equipment', etc with no luck so far. I also tryed with aliases not starting with those two chars but didn't work either because the alias has to send something that starts with 'eq' no matter what I typed in order to do what is supposed to do 
I recompile kmuddy four times and even on diffrent linux distributions since I have Etch && Kubuntu on the same computer. The result is always the same, sometimes it takes longer than others for the error to show up but it is inevitable, quoting agent Smith here
Here is the backtrace of dbg:
Code:
#0 cMXPManager::processResult (this=0x70c0f0, res=0xa319f0) at cmxpmanager.cpp:137
#1 0x000000000044b880 in cMXPManager::processText (this=0x70c0f0, text=<value optimized out>)
at cmxpmanager.cpp:106
#2 0x0000000000429736 in cTextProcessor::parseText (this=0x70d2d0, text=@0x7fff7d540d10)
at ctextprocessor.cpp:133
#3 0x00002b4c2d6da2b6 in cActionManager::invokeEvent (this=0x68d540, event=@0x7fff7d530ca0,
session=1, par1=@0x7fff7d540d10, par2=@0x5cb690) at cactionmanager.cpp:315
#4 0x00002b4c2d6df202 in cActionBase::invokeEvent (this=<value optimized out>,
event=<value optimized out>, session=1, par1=@0x7fff7d540d10, par2=@0x5cb690)
at cactionbase.cpp:131
#5 0x000000000043487e in cTelnet::socketRead (this=0x6dc990) at ctelnet.cpp:1034
#6 0x000000000045b59c in cTelnet::qt_invoke (this=0x6dc990, _id=4, _o=0x7fff7d540f70)
at ctelnet.moc.cpp:95
#7 0x00002b4c2fbfdc26 in QObject::activate_signal () from /usr/lib/libqt-mt.so.3
#8 0x00002b4c2fbfe7b6 in QObject::activate_signal () from /usr/lib/libqt-mt.so.3
#9 0x00002b4c2eb829fd in KNetwork::KBufferedSocket::qt_invoke () from /usr/lib/libkdecore.so.4
#10 0x00002b4c2fbfdc26 in QObject::activate_signal () from /usr/lib/libqt-mt.so.3
#11 0x00002b4c2fbfe60f in QObject::activate_signal () from /usr/lib/libqt-mt.so.3
#12 0x00002b4c2ff6bae0 in QSocketNotifier::activated () from /usr/lib/libqt-mt.so.3
#13 0x00002b4c2fc1f52c in QSocketNotifier::event () from /usr/lib/libqt-mt.so.3
---Type <return> to continue, or q <return> to quit---
#14 0x00002b4c2fb99262 in QApplication::internalNotify () from /usr/lib/libqt-mt.so.3
#15 0x00002b4c2fb9b00c in QApplication::notify () from /usr/lib/libqt-mt.so.3
#16 0x00002b4c2eb4a8be in KApplication::notify () from /usr/lib/libkdecore.so.4
#17 0x00002b4c2fb2c802 in QApplication::sendEvent () from /usr/lib/libqt-mt.so.3
#18 0x00002b4c2fb8bee1 in QEventLoop::activateSocketNotifiers () from /usr/lib/libqt-mt.so.3
#19 0x00002b4c2fb40565 in QEventLoop::processEvents () from /usr/lib/libqt-mt.so.3
#20 0x00002b4c2fbb27ee in QEventLoop::enterLoop () from /usr/lib/libqt-mt.so.3
#21 0x00002b4c2fbb25f7 in QEventLoop::exec () from /usr/lib/libqt-mt.so.3
#22 0x00002b4c2fb9ad40 in QApplication::exec () from /usr/lib/libqt-mt.so.3
#23 0x000000000043de75 in main (argc=<value optimized out>, argv=<value optimized out>)
at main.cpp:118
These are my system specs:
AMD64
1.25 GB ram
Gigabyte board
Radeon 9250 128MB
Linux debian 2.6.18-3-amd64 testing (etch)
KDE 3.5.5
using Kmuddy 0.8
Please help me solve this matter 
PD: Great job, well done, thanks a lot && keep up the good job!
|
|
|
Mecir
KMuddy Author
Group: Administrators
Posts: 1,576
Joined: Feb 2, 2003
|
|
Posted Jan 15, 2007, 1:08 am
|
I'm glad that you like KMuddy !
As for your problem, I've looked at the sources, and I believe that I have found the issue. I'll include the fix in the 0.8.1 bugfix release, which will be ready I-don't-know-when.
If you want, you can fix the issue in your version, so that it works for you right now. Simply open file kmuddy/cmxpmanager.cpp in a text editor, go to line 137, and edit it so it looks like this:
if (s && ((s[0] == 0x1f) && (s[1] == '\0')))
Then run "make" and "make install" again.
Or, you can wait for 0.8.1 to be released.
|
|
.........................
/ Tomas
|
|
Help
Search
Members
