Re: GWorkspace and gcc 4.6

[Riccardo Mottola]

Hi,

"this bug has been known for several years" (wow, did you copy the 
spelling error too?

In fact, GWorkspace has been able to destroy and trash files since a 
while now. I have it compiled also with gcc 4.6 without noticing any 
problems, thus I don't think it is related directly to that.

I will test on a couple of my platforms to check and ask others... to 
test too. Please use SVN since it should contain some fixes (although 
well, if you prove that it works with the last release, perhaps not all 
fixes were painless).

Riccardo

Germán Arias wrote:
> Currently. trying to destroy a file in GWorkspace (from SVN), the app
> freezes. On a terminal I get the error:
>
>
> WARNING your program is becoming multi-threaded, but you are using an
> ObjectiveC runtime library which does not have a thread-safe
> implementation of the +initialize method.  This means that any classes
> not already used may be incorrectly initialised, potentially causing
> strange behaviors and crashes.
> To put this into context, the runtime bug has been knoown for several
> years and
> only rarely causes problems ... the easy workaround being to ensure that
> any classes used by a new thread have already been used in the main
> thread before the new thread starts.
> If you are worried, please build/run GNUstep with a runtime which
> supports the +initialize method. The GNUstep stable runtime (libobjc)
> and experimental runtime (libobjc2), available from the GNUstep website
> and subversion repository, should both work.
> To disable this warning (eg. for an application which does not suffer
> any problems caused by this runtime bug), please set the
> GSSilenceInitializeWarning user default to YES.
>
>
> Even if I set GSSilenceInitializeWarning to YES, the app freezes.
>
>
> _______________________________________________
> Gnustep-dev mailing list
> address@hidden
> https://lists.gnu.org/mailman/listinfo/gnustep-dev
>