gnustep/libs-base
0
0
Fork 0
mirror of https://github.com/gnustep/libs-base.git synced 2025-04-23 00:41:02 +00:00
Code Issues Projects Releases Packages Wiki Activity

Added README.initialize to explain about runtime differences instead of having the log warning.

Browse source 
git-svn-id: svn+ssh://svn.gna.org/svn/gnustep/libs/base/trunk@34003 72102866-910b-0410-8b05-ffd578937521
This commit is contained in:
gcasa 2011-10-15 16:44:19 +00:00
parent f9f11bb060
commit 65f821c32d
2 changed files with 8 additions and 1 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

2
Documentation/GNUmakefile
View file

@ -58,7 +58,7 @@ SUBPROJECTS = manual General
DOCUMENT_TEXT_NAME = \
INSTALL NEWS README ANNOUNCE
TOP_DOC_FILES = INSTALL NEWS README ANNOUNCE
TOP_DOC_FILES = INSTALL NEWS README ANNOUNCE README.initialize
gnustep-base_TEXI_FILES = \
version.texi \

7
Documentation/README.initialize Normal file
View file

@ -0,0 +1,7 @@
The libobjc included with gcc 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.");