[fpc-devel]1. new() bug? 2. another bug i guess :>

[Peter Vreman]

At 23:58 31-5-2003, you wrote:
>Hello again,
>
>It seems that I found 2 bugs(31th May, binary+source snapshot 1.1 , not from
>cvs).
>
>1. new() doesn't allocate memory correctly under specific circumstances,
>    moreover it just crashes with 216 - av.
>
>i had something like this(and it compiled and ran well under 1.0.6):
>
><src>
>...
>TResImageDef        = record
>                         Name      : TResName;   // TResName=string[63]
>                         hName     : longint;
>                         Image     : TImage;
>                         ImgType   : ResImgTypes;
>                       end;
>PResImageDef        = ^TResImageDef;
>...
>ResImageDefs    : array[1..MResImageDefs] of PResImageDef;
>...
>ResImageDefs[nResImageDefs]:=New(PResImageDef);   //   <-------
>ResImageDefs[nResImageDefs]^.Name:=nName;
>...
></src>
>
>the marked line was causing a RE216 but when i changed it into:
>
><src>
>GetMem(ResImageDefs[nResImageDefs],SizeOf(TResImageDef));
>ResImageDefs[nResImageDefs]^.Name:=nName;
></src>
>
>it works well. i dont get it :|.
>(it is quite possible that this code clip works well, but i haven't been
>able
>  to isolate the minimal crashing code :|)
>
>2. i get a following warning message when i try to compile OpenAL headers.
>al.pas(291,4) Warning: c:\fpc\bin\win32\wmvesa\al.ppu Interface CRC changed
>6082E63F<>E1AAF691
>it wouldn't be a problem, if it didn't cause a complete failure eg. my
>simple OpenAL-based engine doesn't work anymore - silence :|.

The 1.1 compiler is currently under heavy development so it can be unstable 
for some parts. We try to keep it as stable as possible but with the 
current number of changes that is sometimes hard.

When you can supply sources we can try to reproduce the problems



Peter