[fpc-pascal] Re: Runs correctly when debugging.

2012-05-10 Thread Guillermo Martínez Jiménez
> No, you have to use pchar. I would also define ALLEGRO_BITMAP as an > empty record, to be clear that it's an opaque type: > > {$packrecords c} > TAllegroBitmap = record > end; > PAllegroBitmap = ^TAllegroBitmap; > > Thus: > > function al_load_bitmap(const filename: pchar): PAllegroBitmap; cde

Re: [fpc-pascal] Re: Runs correctly when debugging.

2012-05-08 Thread Henry Vermaak
On 08/05/12 11:52, Guillermo Martínez Jiménez wrote: >> From: Henry Vermaak >> Subject: Re: [fpc-pascal] Re: Runs correctly when debugging. >> >> It's hard to say without seeing your function/type declarations. > > Actually I don't call the function that ra

[fpc-pascal] Re: Runs correctly when debugging.

2012-05-08 Thread Guillermo Martínez Jiménez
> From: Henry Vermaak > Subject: Re: [fpc-pascal] Re: Runs correctly when debugging. > > It's hard to say without seeing your function/type declarations. Actually I don't call the function that raises the SIGSEGV signal, since it's an internal function. Allegro ha

Re: [fpc-pascal] Re: Runs correctly when debugging.

2012-05-08 Thread Henry Vermaak
On 07/05/12 12:35, Guillermo Martínez Jiménez wrote: > Thanks, Henry, > >> Can you give any more information about how it fails? > > It's a "SIGSEGV". The library is the Allegro library version 5.0.6. > > The error is inside an internal procedure that uploads a texture to > OpenGL context, and

[fpc-pascal] Re: Runs correctly when debugging.

2012-05-07 Thread Guillermo Martínez Jiménez
Thanks, Henry, > Can you give any more information about how it fails? It's a "SIGSEGV". The library is the Allegro library version 5.0.6. The error is inside an internal procedure that uploads a texture to OpenGL context, and it is used by other Allegro functions (i.e. loading pictures from fi