> To make a long story short face->cmap_table is pointing to the wrong
> stuff.
Weird.
> Should base->stream advance by the same number of bytes on both
> platforms?
Yes, I think so. I'm not aware of a single part in FreeType where we
have a different behaviour depending on the platform (except specific
code like the stuff in ftdebug, of course).
> It appears base->stream is set in FT_QMALLOC. I'm wondering if
> something's wrong with my ARM platform's malloc. I'm using the
> newlib C library.
Interesting. On the other hand, it looks implausible that noone has
experienced similar problems with newlib's malloc function... Maybe
there is a bad cast somewhere in the FreeType code.
Any chance to try a different malloc implementation? You might also
activate FreeType's memory debugger (see `docs/DEBUG') for additional
diagnostics.
Werner
_______________________________________________
Freetype mailing list
[email protected]
https://lists.nongnu.org/mailman/listinfo/freetype
