Am Donnerstag, 28. Dezember 2006 02:17 schrieb Giel van Schijndel:
> Dennis Schridde schreef:
> > Am Donnerstag, 28. Dezember 2006 01:42 schrieb Giel van Schijndel:
> >> Dennis Schridde schreef:
> >>> Am Mittwoch, 27. Dezember 2006 23:22 schrieb Giel van Schijndel:
> Dennis Schridde schreef:
>
Am Donnerstag, 28. Dezember 2006 12:07 schrieb Dennis Schridde:
> Am Donnerstag, 28. Dezember 2006 02:17 schrieb Giel van Schijndel:
> > Dennis Schridde schreef:
> > > Am Donnerstag, 28. Dezember 2006 01:42 schrieb Giel van Schijndel:
> > >> Dennis Schridde schreef:
> > >>> Am Mittwoch, 27. Dezembe
Am Donnerstag, 28. Dezember 2006 12:12 schrieb Dennis Schridde:
> Am Donnerstag, 28. Dezember 2006 12:07 schrieb Dennis Schridde:
> > Am Donnerstag, 28. Dezember 2006 02:17 schrieb Giel van Schijndel:
> > > Dennis Schridde schreef:
> > > > Am Donnerstag, 28. Dezember 2006 01:42 schrieb Giel van Sch
Dennis Schridde schreef:
> ...
>
> Fixed now...
Thanks, it works now.
--
Giel
signature.asc
Description: OpenPGP digital signature
___
Warzone-dev mailing list
Warzone-dev@gna.org
https://mail.gna.org/listinfo/warzone-dev
Dennis Schridde schreef:
> Am Donnerstag, 28. Dezember 2006 12:07 schrieb Dennis Schridde:
>
>> Am Donnerstag, 28. Dezember 2006 02:17 schrieb Giel van Schijndel:
>>
A line like
-ljpeg -lpng -lz -lmad -lvorbisfile -lvorbis -logg -lphysfs -lSDLmain
-lSDL -lSDL_net -lGLU -lGL -
Am Donnerstag, 28. Dezember 2006 13:46 schrieb Giel van Schijndel:
> Dennis Schridde schreef:
> > Am Donnerstag, 28. Dezember 2006 12:07 schrieb Dennis Schridde:
> >> Am Donnerstag, 28. Dezember 2006 02:17 schrieb Giel van Schijndel:
> A line like
> -ljpeg -lpng -lz -lmad -lvorbisfile -lv
Dennis Schridde schreef:
> Am Donnerstag, 28. Dezember 2006 13:46 schrieb Giel van Schijndel:
>
>> AFAIK gcc simply runs from left to right, creating a symbol table (of
>> required symbols) on its way, and dropping all unreferenced symbols from
>> memory. This means that you will need to provide
The issue of MALLOC was already raised in some of the previous messages, and
there seems to be something wrong with those MALLOC/FREE macros. I noticed a
memory leak in the scripting engine, to find out what is actually causing it I
set up a (script) loop with 10k iterations with nothing but a s
On Thursday, 28 December 2006 at 15:37, Troman wrote:
> The issue of MALLOC was already raised in some of the previous
> messages, and there seems to be something wrong with those MALLOC/FREE
> macros. I noticed a memory leak in the scripting engine, to find out
> what is actually causing it I set
- Original Message -
From: "Christian Ohm" <[EMAIL PROTECTED]>
To:
Sent: Thursday, December 28, 2006 4:52 PM
Subject: Re: [Warzone-dev] MALLOC/FREE issues
On Thursday, 28 December 2006 at 15:37, Troman wrote:
The issue of MALLOC was already raised in some of the previous
messages,
Am Donnerstag, 28. Dezember 2006 16:52 schrieb Christian Ohm:
> On Thursday, 28 December 2006 at 15:37, Troman wrote:
> > The issue of MALLOC was already raised in some of the previous
> > messages, and there seems to be something wrong with those MALLOC/FREE
> > macros. I noticed a memory leak in
Troman schreef:
> - Original Message - From: "Christian Ohm" <[EMAIL PROTECTED]>
> To:
> Sent: Thursday, December 28, 2006 4:52 PM
> Subject: Re: [Warzone-dev] MALLOC/FREE issues
>> On Thursday, 28 December 2006 at 15:37, Troman wrote:
>>> The issue of MALLOC was already raised in some of
Christian Ohm schreef:
> On Thursday, 28 December 2006 at 1:28, Giel van Schijndel wrote:
>
>> Christian Ohm schreef:
>>
>>> Hm, ok, but if you first fix the code to compile with -Werror that could
>>> be applied indepentently of making it compile with g++.
>>>
>> Sorry, but could y
Am Donnerstag, 28. Dezember 2006 19:56 schrieb Troman:
> - Original Message -
> From: "Christian Ohm" <[EMAIL PROTECTED]>
> To:
> Sent: Thursday, December 28, 2006 4:52 PM
> Subject: Re: [Warzone-dev] MALLOC/FREE issues
>
> > On Thursday, 28 December 2006 at 15:37, Troman wrote:
> >> The i
Am Donnerstag, 28. Dezember 2006 20:15 schrieb Giel van Schijndel:
> Christian Ohm schreef:
> > On Thursday, 28 December 2006 at 1:28, Giel van Schijndel wrote:
> >> Christian Ohm schreef:
> >>> Hm, ok, but if you first fix the code to compile with -Werror that
> >>> could be applied indepentently
Am Donnerstag, 28. Dezember 2006 20:10 schrieb Giel van Schijndel:
> Troman schreef:
> > - Original Message - From: "Christian Ohm" <[EMAIL PROTECTED]>
> > To:
> > Sent: Thursday, December 28, 2006 4:52 PM
> > Subject: Re: [Warzone-dev] MALLOC/FREE issues
> >
> >> On Thursday, 28 December
Dennis Schridde schreef:
> Am Donnerstag, 28. Dezember 2006 20:10 schrieb Giel van Schijndel:
>
>> Troman schreef:
>>
>>> - Original Message - From: "Christian Ohm" <[EMAIL PROTECTED]>
>>> To:
>>> Sent: Thursday, December 28, 2006 4:52 PM
>>> Subject: Re: [Warzone-dev] MALLOC/FREE
This patch does exactly as its filename suggest: only deleting (unused)
stuff.
I've only deleted functions and variables in this patch that triggered a
warning (i.e. they weren't even referred to in their respective include
header files).
--
Giel
Index: lib/framework/block.c
Troman schreef:
- Original Message - From: "Christian Ohm" <[EMAIL PROTECTED]>
To:
Sent: Thursday, December 28, 2006 4:52 PM
Subject: Re: [Warzone-dev] MALLOC/FREE issues
On Thursday, 28 December 2006 at 15:37, Troman wrote:
The issue of MALLOC was already raised in some of the previou
On Thursday, 28 December 2006 at 20:06, Dennis Schridde wrote:
> I think not too long ago Per said something like simply replacing MALLOC was
> not possible... Dunno if I remember that correctly or how his patch fixed
> that...
Just defining MALLOC/FREE to malloc/free etc. (see below) compiles a
Christian Ohm schreef:
> On Thursday, 28 December 2006 at 20:06, Dennis Schridde wrote:
>
>> I think not too long ago Per said something like simply replacing MALLOC was
>> not possible... Dunno if I remember that correctly or how his patch fixed
>> that...
>>
>
> Just defining MALLOC/FRE
Giel van Schijndel schreef:
> Christian Ohm schreef:
>
>> On Thursday, 28 December 2006 at 20:06, Dennis Schridde wrote:
>>
>>
>>> I think not too long ago Per said something like simply replacing MALLOC
>>> was
>>> not possible... Dunno if I remember that correctly or how his patch fi
22 matches
Mail list logo
