Subject: Re: [Openocd-development] malloc: Vote what to do
>
> On Thu, 2009-12-17 at 21:44 +0100, Carsten Breuer wrote:
> > Hi all,
> >
> >
> > after finding out, that malloc come back with NULL
> > even on linux (where people says here, it don't),
> > im sta
mount of memory. Killing the app is not a good idea I think. Again
this is probably me thinking "embedded" rather than PC.
--
Liam.
- Original Message -
From: "Carsten Breuer"
To:
Sent: Thursday, December 17, 2009 8:44 PM
Subject: [Openocd-development] malloc: Vote wh
On Thu, 2009-12-17 at 21:44 +0100, Carsten Breuer wrote:
> Hi all,
>
>
> after finding out, that malloc come back with NULL
> even on linux (where people says here, it don't),
> im starting to loose interest in the hole thing.
>
> So what should we do?
>
> I think now, that all this arguments n
On Thursday 17 December 2009, Øyvind Harboe wrote:
> As a maintainer I would summarize the status quo as(and there
> are no plans to change this):
>
> - accept all clean patches to fix propagation of error handling.
> malloc() is just one example of broken error propagation
>
> - leave malloc()'s
As a maintainer I would summarize the status quo as(and there
are no plans to change this):
- accept all clean patches to fix propagation of error handling.
malloc() is just one example of broken error propagation
- leave malloc()'s as-is meanwhile, we have tools to identify
the cases where we're
Carsten Breuer wrote:
> Hi all,
>
Hi!
> after finding out, that malloc come back with NULL
> even on linux (where people says here, it don't),
It does, but it's a tricky topic. Please post your test program!
I've tried this one on Ubuntu 9.10 in VirtualBox:
#include
#include
#include
Hi all,
after finding out, that malloc come back with NULL
even on linux (where people says here, it don't),
im starting to loose interest in the hole thing.
So what should we do?
I think now, that all this arguments not to check
malloc result is academical and some arguments are not
even true.
