On 01/04/2013 08:53 AM, Noel Grandin wrote:
Why are we catching std::bad_alloc all over the place?
git grep 'catch.*bad_alloc' | wc -l
68
Surely we should just let it crash?
Or have a single handler for the whole process that at least attempts to
provide some debugging data
On 04/01/13 08:53, Noel Grandin wrote:
Why are we catching std::bad_alloc all over the place?
git grep 'catch.*bad_alloc' | wc -l
68
Surely we should just let it crash?
Or have a single handler for the whole process that at least attempts to
provide some debugging data
On 01/04/2013 08:53 AM, Noel Grandin wrote:
Why are we catching std::bad_alloc all over the place?
git grep 'catch.*bad_alloc' | wc -l
68
Surely we should just let it crash?
Or have a single handler for the whole process that at least attempts to
provide some debugging data?
I
Why are we catching std::bad_alloc all over the place?
git grep 'catch.*bad_alloc' | wc -l
68
Surely we should just let it crash?
Or have a single handler for the whole process that at least attempts to
provide some debugging data?
At the moment, most of them just log something
