Re: Weirdness with FT_Alloc [was: OpenType with CFF outlines]

[Tom Kacvinsky]

When I get the code to compile with DEC's C compiler (versus gcc),
I can then add some code that will cause ftview to dump core when
a misalignment happens.  I can then bt in gdb and get more information
for you.

The reason why DEC's C compiler is choking on the freetype code is
because DEC C doesn't like constructs like

#if ...

   #define

#endif

The # has to line up in the left column.  Perhaps there is a compiler flag
I can use to get rid of the problem.  Or I can perly-whirly the code
to left align the # in the macro directives...

Tom

On Tue, 27 Jun 2000, Werner LEMBERG wrote:

> 
> > Speaking of Alphas, I tried freetype2's latest snapshot on a DEC
> > Unix box (can't stand the name Tru64 UNIX), and got all kins of
> > unaligned access errors.  Ghostscript used to get these all of the
> > time, and it was because of weirdness in memory allocation
> > (returning pointers that didn't align on an 8 byte boundary).
> 
> This shouldn't happen.  Can you give more details?  Some hot spots
> where this happens?  We have an `FT_ALIGNMENT' macro (set to 8 by
> default) which probably has to be used more often...
> 
> 
>     Werner
>