The bug is in the GCC Objective-C runtime. The runtime is responsible for ensuring that +initialize is thread safe. The 'fix' is to use the GNUstep runtime as well. Is there a reason why you're using GCC for Objective-C code?
David On 12 Aug 2014, at 03:48, Amr Aboelela <amraboel...@gmail.com> wrote: > Did you guys fix this issue? > > I suspect the problem might be in the implementation of the +[NSObject > initialize] itself. > > > On Sun, Jul 20, 2014 at 7:06 PM, Germán Arias <germanan...@gmx.es> wrote: > On 2014-07-20 09:18:26 -0600 Ivan Vučica <i...@vucica.net> wrote: > > > Which runtime are you using? > > > > > > The runtime that comes with gcc 4.6.3. > > Germán. > > > _______________________________________________ > Gnustep-dev mailing list > Gnustep-dev@gnu.org > https://lists.gnu.org/mailman/listinfo/gnustep-dev > > > > -- > Info about Islam: http://wikiz.info/islam > > _______________________________________________ > Gnustep-dev mailing list > Gnustep-dev@gnu.org > https://lists.gnu.org/mailman/listinfo/gnustep-dev -- Sent from my Difference Engine _______________________________________________ Gnustep-dev mailing list Gnustep-dev@gnu.org https://lists.gnu.org/mailman/listinfo/gnustep-dev
