Re: [E-devel] e_malloc ?

2012-09-05 Thread The Rasterman
On Wed, 5 Sep 2012 13:09:42 +0100 Michael Blumenkrantz said: > in applications? nothing. and in e - same. nothing. checking every single one is a lot of work and abort is unacceptable for a wm. > On Wed, Sep 5, 2012 at 12:52 PM, rustyBSD wrote: > > > Le 04/09/2012 01:54, Carsten Haitzler (The

Re: [E-devel] e_malloc ?

2012-09-05 Thread Michael Blumenkrantz
in applications? nothing. On Wed, Sep 5, 2012 at 12:52 PM, rustyBSD wrote: > Le 04/09/2012 01:54, Carsten Haitzler (The Rasterman) a écrit : > > agreed. if u abort() or segv() it makes little difference. for small data > > structs (linked list nodes for example) its VERY hard to recover > sensib

Re: [E-devel] e_malloc ?

2012-09-05 Thread rustyBSD
Le 04/09/2012 01:54, Carsten Haitzler (The Rasterman) a écrit : > agreed. if u abort() or segv() it makes little difference. for small data > structs (linked list nodes for example) its VERY hard to recover sensibly from > such an out-of-memory situation. but for large allocs its perfectly possible

Re: [E-devel] e_malloc ?

2012-09-03 Thread Cedric BAIL
On Tue, Sep 4, 2012 at 8:54 AM, Carsten Haitzler wrote: > On Mon, 3 Sep 2012 18:45:58 -0300 Gustavo Sverzut Barbieri > said: >> Really bad >> >> -1000 > > agreed. if u abort() or segv() it makes little difference. for small data > structs (linked list nodes for example) its VERY hard to recover s

Re: [E-devel] e_malloc ?

2012-09-03 Thread The Rasterman
On Mon, 3 Sep 2012 18:45:58 -0300 Gustavo Sverzut Barbieri said: > Really bad > > -1000 agreed. if u abort() or segv() it makes little difference. for small data structs (linked list nodes for example) its VERY hard to recover sensibly from such an out-of-memory situation. but for large allocs

Re: [E-devel] e_malloc ?

2012-09-03 Thread Gustavo Sverzut Barbieri
Really bad -1000 On Monday, September 3, 2012, Daniel Juyung Seo wrote: > Anyway the system will crash if it fails to allocate memory. > But +1 here. Doing exception handling is a good practice. > > Daniel Juyung Seo (SeoZ) > > On Tue, Sep 4, 2012 at 3:49 AM, rustyBSD > > wrote: > > Hi, > > in a

Re: [E-devel] e_malloc ?

2012-09-03 Thread Daniel Juyung Seo
Anyway the system will crash if it fails to allocate memory. But +1 here. Doing exception handling is a good practice. Daniel Juyung Seo (SeoZ) On Tue, Sep 4, 2012 at 3:49 AM, rustyBSD wrote: > Hi, > in a lot of files, we use calloc(), malloc(), > realloc(), ... > > Wouldn't it be good to have s

[E-devel] e_malloc ?

2012-09-03 Thread rustyBSD
Hi, in a lot of files, we use calloc(), malloc(), realloc(), ... Wouldn't it be good to have stuffs like g_malloc() which aborts when it cannot allocate memory ? Because there are a lot of un-null-checked calls, which could be problematic... ---