I am at work right now, so there is little I can do from herr. The problem is in -_reserUDateFormat. I assume the udat_open function is failing on your system. Would you mind confirming this is the problem? The udat_open function should always return something useful. On Nov 27, 2012 7:57 AM, "Gregory Casamento" <[email protected]> wrote:
> Hey guys, > > I am having a problem starting up Gorm on Windows. I have traced it to > this section of code in NSDateFormatter... > > 125 > 126 length = udat_toPattern (internal->_formatter, 0, NULL, 0, > &err); > 127 value = NSZoneMalloc (z, sizeof(unichar) * length); > 128 err = U_ZERO_ERROR; > 129 udat_toPattern (internal->_formatter, 0, value, length, &err); > > The issue is that length is coming back as -1, which, when the > NSZoneMalloc tries to allocate ends up trying to allocate all available > memory since the value is interpreted as unsigned. > > The only reason Gorm gets this issue and the other apps I tested don't > is due to the fact that none of the others attempt to use NSDateFormatter. > > GC > -- > Gregory Casamento > Open Logic Corporation, Principal Consultant > yahoo/skype: greg_casamento, aol: gjcasa > (240)274-9630 (Cell) > http://www.gnustep.org > http://heronsperch.blogspot.com > > _______________________________________________ > Gnustep-dev mailing list > [email protected] > https://lists.gnu.org/mailman/listinfo/gnustep-dev > >
_______________________________________________ Gnustep-dev mailing list [email protected] https://lists.gnu.org/mailman/listinfo/gnustep-dev
