From: Aaron B. <bo...@gm...> - 2017-08-04 15:34:49
|
Thanks, guys. In this particular case, I think the problem is just using a signed int to store something that always be positive: fl->nFunctions and c->ParameterCount[Pos] On Fri, Aug 4, 2017 at 8:51 AM, Bob Friesenhahn < bfr...@si...> wrote: > On Fri, 4 Aug 2017, Martí Maria wrote: > > >> Hi Bob, >> >> Thanks for pointing out this. Yes, x64 is supported and tested. I have >> done a search of "size_t" and the core library does not use it, nor >> unsigned long. The places where integer overflow can happen are known, as >> this may represent a security risk. >> > > Size_t is implicitly used by memcpy(), malloc(), and other OS functions > which require a size type. Doing size computations using the size_t type > is not a bad thing, especially if it feeds an interface already using the > size_t type. > > On the flip side, Windows provides only a 32-bit stdio API (even in a > 64-bit build), which results in more opportunity for problems. > > > Bob > -- > Bob Friesenhahn > bfr...@si..., http://www.simplesystems.org/users/bfriesen/ > GraphicsMagick Maintainer, http://www.GraphicsMagick.org/ > > ------------------------------------------------------------ > ------------------ > Check out the vibrant tech community on one of the world's most > engaging tech sites, Slashdot.org! http://sdm.link/slashdot > _______________________________________________ > Lcms-user mailing list > Lcm...@li... > https://lists.sourceforge.net/lists/listinfo/lcms-user > > |