gnustep errors in log

For test results, bug reports, announcements of new builds etc.

Moderators: winston, another_commander, Getafix

Post Reply
User avatar
tinker
Deadly
Deadly
Posts: 166
Joined: Tue Jul 22, 2008 7:45 am
Location: Sachsen

gnustep errors in log

Post by tinker »

Running a shiney new 1.77 (x86-64 test release) under Linux 3.6.8-1-ARCH these 2 errors keep popping up.

16:24:44.211 [shipData.load.begin]: Loading ship data.
16:24:44.219 [gnustep]: 2013-01-11 16:24:44.219 oolite[7485] File NSPropertyList.m: 1012. In parsePlItem Missing semicolon in dictionary at line 932 char 19991

16:24:44.473 [gnustep]: 2013-01-11 16:24:44.473 oolite[7485] File NSPropertyList.m: 1012. In parsePlItem Missing semicolon in dictionary at line 18 char 360
Semper Dissimilis
User avatar
cim
Quite Grand Sub-Admiral
Quite Grand Sub-Admiral
Posts: 4072
Joined: Fri Nov 11, 2011 6:19 pm

Re: gnustep errors in log

Post by cim »

tinker wrote:
16:24:44.211 [shipData.load.begin]: Loading ship data.
16:24:44.219 [gnustep]: 2013-01-11 16:24:44.219 oolite[7485] File NSPropertyList.m: 1012. In parsePlItem Missing semicolon in dictionary at line 932 char 19991

16:24:44.473 [gnustep]: 2013-01-11 16:24:44.473 oolite[7485] File NSPropertyList.m: 1012. In parsePlItem Missing semicolon in dictionary at line 18 char 360
One, or perhaps two of your OXPs, has a badly formatted openstep-style plist. Somewhere, it will have:

Code: Select all

something = "something else"
}
rather than

Code: Select all

something = "something else";
}
. On Linux, this is harmless. On Macs, it will probably break the OXP. So it should be reported to the maintainer.

Unfortunately, the error tells you which line the error was on (and what character position in the file), but not which file it was in. Short of doing the usual "remove half your OXPs" trick, tracking it down further will be very difficult.
Post Reply