For test results, bug reports, announcements of new builds etc.
Moderators: winston , another_commander , Getafix
Thargoid
Thargoid
Posts: 5528 Joined: Thu Jun 12, 2008 6:55 pm
Post
by Thargoid » Tue Jun 16, 2009 7:42 am
another_commander wrote: Standard methodology: Start with an empty AddOns folder, then add one by one Nemoricus' oxps, restarting after adding each, until your log reports the error.
Faster methodology (on average) - add half the OXPs back. If problem appears, remove half of those. If it doesn't add half of the remaining OXPs. Repeat adding/removing single OXP makes issue re-appear/disappear.
Same technique, but a faster way of doing it normally, if a little more complicated to track.
Screet
---- E L I T E ----
Posts: 1883 Joined: Wed Dec 10, 2008 3:02 am
Location: Bremen, Germany
Post
by Screet » Tue Jun 16, 2009 11:56 am
Svengali wrote: [gnustep]: 2009-06-14 20:30:34.656 oolite[4932] could not convert to UTF8 string! bytes=04911c59 len=6
Doesn't look good and after that point everything can happen, I think.
The interesting part of this is, that I get the same error for some time now - but the values differ without changes to the OXPs!
The values in oolite[x] and bytes=y do change, but len=6 always stays.
It does not seem to cause harm, though.
Screet
JensAyton
Grand Admiral Emeritus
Posts: 6657 Joined: Sat Apr 02, 2005 2:43 pm
Location: Sweden
Contact:
Post
by JensAyton » Tue Jun 16, 2009 1:04 pm
Lestradae wrote: Misunderstanding, I meant how could this error be produced by an oxp, in other words: If I searched for it, what eactly would I be looking for?
You’d be looking for that message appearing in the log. :-)
Screet wrote: The interesting part of this is, that I get the same error for some time now - but the values differ without changes to the OXPs!
The values in oolite[x] and bytes=y do change, but len=6 always stays.
Hmm, if the bytes value is changing something nasty’s going on.