On Wed, 13 Jun 2007 17:31:17 -0400 Dennis Schridde
<[EMAIL PROTECTED]> wrote:
>Am Mittwoch, 13. Juni 2007 schrieb [EMAIL PROTECTED]:
>> The game crash on that line, free(image->bmp).
>> Since it set to NULL after 1st free call, we can then assume
>that
>> image pointer is wrong/corrupted.
>> So t
Am Mittwoch, 13. Juni 2007 schrieb [EMAIL PROTECTED]:
> On Wed, 13 Jun 2007 16:54:33 -0400 Giel van Schijndel
>
> <[EMAIL PROTECTED]> wrote:
> >Dennis Schridde schreef:
> >>> Index: tex.c
> >
> >===
> >
> >>> --- tex.c (revision 1494)
On Wed, 13 Jun 2007 16:54:33 -0400 Giel van Schijndel
<[EMAIL PROTECTED]> wrote:
>Dennis Schridde schreef:
>>> Index: tex.c
>>>
>===
>
>>> --- tex.c (revision 1494)
>>> +++ tex.c (working copy)
>>> @@ -264,7 +264,7 @@
>>>
>>> vo
Dennis Schridde schreef:
> Am Mittwoch, 13. Juni 2007 schrieb [EMAIL PROTECTED]:
>
>> I no could tell where original function came from. It was add to
>> tex.c from ???
>> It crash for me with free memory already free.
>> So this fix it.
>>
>> Also, I find that lots physfs routines that use cop
Am Mittwoch, 13. Juni 2007 schrieb [EMAIL PROTECTED]:
> I no could tell where original function came from. It was add to
> tex.c from ???
> It crash for me with free memory already free.
> So this fix it.
>
> Also, I find that lots physfs routines that use copy, use uninit
> variables, but no seem
[EMAIL PROTECTED] schreef:
> I no could tell where original function came from. It was add to
> tex.c from ???
> It crash for me with free memory already free.
> So this fix it.
>
> Index: tex.c
> ===
> --- tex.c (revision 1494)
I no could tell where original function came from. It was add to
tex.c from ???
It crash for me with free memory already free.
So this fix it.
Also, I find that lots physfs routines that use copy, use uninit
variables, but no seem to be problem?
Index: tex.c
==
