discuss-gnustep
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: gnustep making me crazy


From: Richard Frith-Macdonald
Subject: Re: gnustep making me crazy
Date: Tue, 7 May 2002 06:48:35 +0100

On Monday, May 6, 2002, at 07:29 PM, Kees Cook wrote:

Okay, after massive compiler upgrades, I have everything
compiled and installed.  However, I haven't yet been able to launch an
app.  Most fail like so:

[nemesis@ghostship Calculator]$ openapp Calculator.app
/scratch/gnustep/gnustep-
examples-0.9.5/gui/Calculator/Calculator.app/ix86/linux-gnu/gnu-gnu-
gnu/Calculator:
Uncaught exception NSInternalInconsistencyException, reason: class list
improperly terminated

I've never seen or heard of this happening ... the above error message occurs only in two places ... when unarchiving data and when deserialising an object sent from another process. I'm pretty sure that Calculator does not use any archives, so I guess this could only be part of it trying to tell the distributed notification centre that it has started running, and either the data it send to gdnc being
corrupt or the data it receives back being corrupt.
I can't really see how that can happen unless by some strange freak of chance, gdnc crashed, and some other non-gnustep process started using its port, so everything trying to connect to gdnc is actually talking to some non-gnustep network process.

You could try making sure that gdomap (and gdnc ad gpbs if running) is restarted.

If that fails, you could try running with --GNU-Debug=GSTcpHandle and --GNU-Debug=NSPort
to see what data is actually being transferred between the processes.

And some don't even build correctly:

[nemesis@ghostship ProcViewer]$ make
Making all for app ProcViewer...
May 06 11:26:57 plmerge[7543] Parsing 'ProcViewerInfo.plist' - Parse
failed at line 1 (char 14) - extra data after parsed string
make[1]: *** [ProcViewer.app/Resources/Info-gnustep.plist] Error 139
make: *** [ProcViewer.all.app.variables] Error 2

That just looks like there is some bogus data in ProcViewerInfo.plist
try editing it to see.




reply via email to

[Prev in Thread] Current Thread [Next in Thread]