seg fault on checking the rift

User avatar
Vadi
Posts: 4732
Joined: Sat Mar 14, 2009 3:13 pm

Re: seg fault on checking the rift

Post by Vadi » Sun Dec 02, 2012 6:20 am

No, just need them for Mudlet - it would require you to build it yourself, since I reckon the one from Arch Linux repositories has the function calls stripped of names.

User avatar
chris
Posts: 493
Joined: Fri Jun 17, 2011 5:39 am

Re: seg fault on checking the rift

Post by chris » Sun Dec 02, 2012 11:48 pm

Well since you can run gdb, have you tried running in debug mode within Qt Creator? If the error's in Mudlet's design, it will be traceable in there (but if its a 3rd party, probably not)

azinulbizar
Posts: 13
Joined: Fri Aug 10, 2012 11:25 pm

Re: seg fault on checking the rift

Post by azinulbizar » Mon Dec 03, 2012 1:49 am

For some reason I can't compile under debian wheezy, have all the dev libraries, it's throwing some weird errors and I don't know what they are. As for the deb package debugging in qt creator, it's still the same output.

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

Re: seg fault on checking the rift

Post by Heiko » Mon Dec 03, 2012 6:16 pm

1. Can you reproduce this on a clean profile without any installed packages/scripts or systems?

2. For Debian you can install the source code package for the underlying official Debian package. This will compile for sure.

Mael
Posts: 1
Joined: Thu Feb 28, 2013 10:42 am

Re: seg fault on checking the rift

Post by Mael » Thu Feb 28, 2013 10:44 am

Okay, I know this is an old thread, but this just started happening to me. I check IR and Mudlet crashes. I tried reinstalling both Svo and Mudlet, and it still does it. :/

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

Re: seg fault on checking the rift

Post by Heiko » Thu Feb 28, 2013 11:20 am

This is due to a bug in Mudlet. The fix will be available when Mudlet 2.2 will be released. There are known workarounds now and I'm sure Vadi will update svo soon. Until then you can use this workaround: The crash only happens if the last line of your rift display has an empty item at the end and 99% or so of your items are shown before more. Add some more items to your rift or drop a few and you'll be fine until svo has been updated with a proper workaround.

Post Reply

Who is online

Users browsing this forum: No registered users and 5 guests