another mudlet osx crash

Post Reply
osxuser
Posts: 5
Joined: Fri Aug 27, 2010 7:12 pm

another mudlet osx crash

Post by osxuser »

Here's another crash that keeps popping up at random, not sure what triggers it as I'm usually afk and have mudlet sitting around in the background when it happens...


Process: mudlet [81291]
Path: /Applications/Mudlet 1.1.app/Contents/MacOS/./mudlet
Identifier: org.mudlet.client
Version: ??? (???)
Code Type: X86 (Native)
Parent Process: bash [81288]

Date/Time: 2010-09-08 18:41:27.563 -0700
OS Version: Mac OS X 10.6.4 (10F569)
Report Version: 6

Interval Since Last Report: 81424 sec
Crashes Since Last Report: 2
Per-App Interval Since Last Report: 61186 sec
Per-App Crashes Since Last Report: 2
Anonymous UUID: 31993A0B-73B9-43C7-9DA5-B77F63D94E55

Exception Type: EXC_BAD_ACCESS (SIGSEGV)
Exception Codes: KERN_INVALID_ADDRESS at 0x0000000080000019
Crashed Thread: 0 Dispatch queue: com.apple.main-thread

Thread 0 Crashed: Dispatch queue: com.apple.main-thread
0 mudlet 0x0018f6e1 TBuffer::copy(QPoint&, QPoint&) + 449
1 mudlet 0x00011814 TConsole::copy() + 68
2 mudlet 0x000be541 TLuaInterpreter::copy(lua_State*) + 225
3 mudlet 0x001a9483 luaD_precall + 355
4 mudlet 0x001b49ae luaV_execute + 4686
5 mudlet 0x001a98c0 luaD_call + 192
6 mudlet 0x001a5321 f_call + 33
7 mudlet 0x001a8d9b luaD_rawrunprotected + 59
8 mudlet 0x001a9be2 luaD_pcall + 66
9 mudlet 0x001a5395 lua_pcall + 101
10 mudlet 0x000d26c7 TLuaInterpreter::call(QString&, QString&) + 311
11 mudlet 0x000a209f TTrigger::execute() + 191
12 mudlet 0x000acb93 TTrigger::match_perl(char*, QString&, int, int) + 3379
13 mudlet 0x000a934c TTrigger::match(char*, QString&, int, int) + 1884
14 mudlet 0x000a9a31 TTrigger::match(char*, QString&, int, int) + 3649
15 mudlet 0x000a9a31 TTrigger::match(char*, QString&, int, int) + 3649
16 mudlet 0x000a9a31 TTrigger::match(char*, QString&, int, int) + 3649
17 mudlet 0x000b1088 TriggerUnit::processDataStream(QString&, int) + 264
18 mudlet 0x000364cc Host::incomingStreamProcessor(QString&, QString&, int) + 44
19 mudlet 0x000092cc TConsole::runTriggers(int) + 572
20 mudlet 0x00191874 TBuffer::translateToPlainText(std::string&) + 1540
21 mudlet 0x00020001 TConsole::printOnDisplay(std::string&) + 145
22 mudlet 0x00031ae4 cTelnet::gotRest(std::string&) + 260
23 mudlet 0x00032745 cTelnet::handle_socket_signal_readyRead() + 853
24 mudlet 0x0019cbff cTelnet::qt_metacall(QMetaObject::Call, int, void**) + 223
25 QtCore 0x013a7d1a QMetaObject::activate(QObject*, QMetaObject const*, int, void**) + 570
26 QtCore 0x014d68e2 QIODevice::readyRead() + 50
27 QtNetwork 0x0128f262 QAbstractSocketPrivate::canReadNotification() + 770
28 QtNetwork 0x0127d9cb QReadNotifier::event(QEvent*) + 59
29 QtGui 0x006d34bf QApplicationPrivate::notify_helper(QObject*, QEvent*) + 175
30 QtGui 0x006d943b QApplication::notify(QObject*, QEvent*) + 379
31 QtCore 0x013a2492 QCoreApplication::notifyInternal(QObject*, QEvent*) + 98
32 QtGui 0x0067f3aa qt_mac_socket_callback(__CFSocket*, CFSocketCallBackType, __CFData const*, void const*, void*) + 154
33 com.apple.CoreFoundation 0x975d918e __CFSocketDoCallback + 702
34 com.apple.CoreFoundation 0x975d8c77 __CFSocketPerformV0 + 311
35 com.apple.CoreFoundation 0x975930fb __CFRunLoopDoSources0 + 1563
36 com.apple.CoreFoundation 0x97590bbf __CFRunLoopRun + 1071
37 com.apple.CoreFoundation 0x97590094 CFRunLoopRunSpecific + 452
38 com.apple.CoreFoundation 0x9758fec1 CFRunLoopRunInMode + 97
39 QtGui 0x0067f850 QEventDispatcherMac::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) + 512
40 QtCore 0x0147f441 QEventLoop::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) + 65
41 QtCore 0x0147f66d QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) + 189
42 QtCore 0x014819ce QCoreApplication::exec() + 174
43 mudlet 0x00034f1b main + 5659
44 mudlet 0x00006bad _start + 208
45 mudlet 0x00006adc start + 40

User avatar
Heiko
Site Admin
Posts: 1548
Joined: Wed Mar 11, 2009 6:26 pm

Re: another mudlet osx crash

Post by Heiko »

Which version of Mudlet are you on? This looks like a real bug in Mudlet code. I'll look into it.
Until then, disable the regex trigger that uses copy() and please post both the perl regex pattern + the trigger script.
Can it be that you have forgotten to select the text that you want to copy and just call copy without any selected text or that the old text selection before copy still refers to some text that has been gagged before by other trigs?

osxuser
Posts: 5
Joined: Fri Aug 27, 2010 7:12 pm

Re: another mudlet osx crash

Post by osxuser »

mudlet 1.1

I'm using a third party set of scripts that create chat/status/etc windows and I'm not sure exactly which copy() call is causing the crash

if you are interested it's here:

http://www.aardwolf.com/wiki/uploads/MAG_110.zip
http://www.aardwolf.com/wiki/index.php/ ... I#Download

I'm not sure how to reproduce it besides letting the mud client idle for hours till it happens

Post Reply