Segfault in MAC OS X

[Toadkin]

I went backpacking for about a week and upon return I noticed that Lich segfaults about half the time. I'm running Snow Leopard, and here is the terminal output:



$sudo ruby Documents/Simutronics/lich/lich.rbw --gemstone --avalon
Xlib: extension "RANDR" missing on display "/tmp/launch-jc2pIv/org.x:0".
Pretending to be gs3.simutronics.net
Listening on port 4900
Waiting for the client to connect...
Connection with the local game client is open.
Documents/Simutronics/lich/lich.rbw:2190: [BUG] Segmentation fault
ruby 1.8.7 (2010-06-23 patchlevel 299) [x86_64-darwin10]

Abort trap


Typically what happens is I can log into Lich through one instance of Avalon fine, but then I'll try to fire up another instance of Lich and that one gets the segfault. All instances of Lich started after this point (even after logging out/shutting down previous instances of Lich) will segfault. Is there something I can do?

[Daragon]

I went backpacking for about a week and upon return I noticed that Lich segfaults about half the time. I'm running Snow Leopard, and here is the terminal output:

Another reason MAC will never beat PC no matter how big the hype is..
My diagnosis: Get a PC.

[Toadkin]

After dicking around for awhile I'm lead to believe that the segfault had something to do with some script's settings. I did a clean install of Lich and everything worked, but as soon as I tried to import my old data the same segfault occurred.

[Daragon]

After dicking around for awhile I'm lead to believe that the segfault had something to do with some script's settings. I did a clean install of Lich and everything worked, but as soon as I tried to import my old data the same segfault occurred.

Probably had a corrupted file in your old data. Might just need to start fresh...

[Donquix]

did you download FUCKMACS.lic?

[Toadkin]

For what it's worth, I'm almost positive the issue had/has something to do with asloot/sloot. Previous to this morning, I could trigger the segfault whenever I setup asloot and then tried to log back in. As of this morning, the segfault triggered after I updated and configured sloot.