Page 1 of 1

Mudlet 3.0 crashes when trying to delete rooms

Posted: Mon Jan 13, 2014 9:38 pm
by Filion
Segmentation Fault, running from terminal.

Re: Mudlet 3.0 crashes when trying to delete rooms

Posted: Mon Jan 13, 2014 9:51 pm
by xabre
Hmm, that doesn't help much, and there should be way more output than just that. Also, I presume you're using curent git master which is a unstable version of Mudlet, bugs are expected. Have you tried older, stable, Mudlet 2.1?

Re: Mudlet 3.0 crashes when trying to delete rooms

Posted: Mon Jan 13, 2014 11:29 pm
by Filion
This is a part of the output in terminal. I do think that seg fault is a bit indepedent.
Code: [show] | [select all] lua
QPainter::begin: Paint device returned engine == 0, type: 2
QPainter::begin: Paint device returned engine == 0, type: 2
QPainter::begin: Paint device returned engine == 0, type: 2
QPainter::begin: Paint device returned engine == 0, type: 2
QPainter::begin: Paint device returned engine == 0, type: 2
QPainter::begin: Paint device returned engine == 0, type: 2
QPainter::begin: Paint device returned engine == 0, type: 2
QPainter::begin: Paint device returned engine == 0, type: 2
QPainter::begin: Paint device returned engine == 0, type: 2
x= 49  y= 3066 
x= 106  y= 9064 
x= 70  y= 9145 
addRoom( 17027 ) 
addRoom( 17028 ) 
addRoom( 17029 ) 
addRoom( 17030 ) 
x= 81  y= 9851 
x= 80  y= 9032 
x= 76  y= 9186 
x= 43  y= 9746 
x= 83  y= 9036 
x= 96  y= 9824 
x= 60  y= 9260 
Segmentation fault
I am using the current git master, indeed as I don't want some things like nil characters on the client, as they conflict on some of my scripts.

Re: Mudlet 3.0 crashes when trying to delete rooms

Posted: Tue Jan 14, 2014 7:37 pm
by Vadi
nil characters?

Re: Mudlet 3.0 crashes when trying to delete rooms

Posted: Wed Jan 15, 2014 12:55 am
by Filion
When I was logging on my mud, some characters were shown on notepad++ as nil. I think it was CR characters.

Re: Mudlet 3.0 crashes when trying to delete rooms

Posted: Wed Jan 15, 2014 2:37 am
by chris
If you are running the development version and reporting bugs, you want to ensure they are not occurring in the development branch (the 'master' branch points to SourceForge which is significantly behind)