From b8f9f92731e875647c18ba1e7e7a48bf699d9ad0 Mon Sep 17 00:00:00 2001 From: Alexander Boettcher Date: Thu, 24 Nov 2016 10:28:16 +0100 Subject: [PATCH] base: remove allocation warning in heap The heap typically first tries to allocate larger chunks than necessary, and if it fails the actual minimal one. The first attempt already triggers warnings which are not critical at all. If the second (critical) allocation fails, then there are additionally checks and warnings already in place. Issue #1039 --- repos/base/src/lib/base/heap.cc | 1 - 1 file changed, 1 deletion(-) diff --git a/repos/base/src/lib/base/heap.cc b/repos/base/src/lib/base/heap.cc index b737a0d7d..252e79c95 100644 --- a/repos/base/src/lib/base/heap.cc +++ b/repos/base/src/lib/base/heap.cc @@ -90,7 +90,6 @@ Heap::Dataspace *Heap::_allocate_dataspace(size_t size, bool enforce_separate_me new_ds_cap = _ds_pool.ram_session->alloc(size); ds_addr = _ds_pool.region_map->attach(new_ds_cap); } catch (Ram_session::Alloc_failed) { - warning("could not allocate new dataspace of size ", size); return 0; } catch (Region_map::Attach_failed) { warning("could not attach dataspace");