From 0e074306a9a9f4b163e78f6ab9648a1097ea77f2 Mon Sep 17 00:00:00 2001
From: Joe Thornber <ejt@redhat.com>
Date: Wed, 26 Jun 2013 11:28:36 +0100
Subject: [PATCH] Document unit test issue with g++ 4.8.1

---
 unit-tests/block_t.cc | 5 +++++
 1 file changed, 5 insertions(+)

diff --git a/unit-tests/block_t.cc b/unit-tests/block_t.cc
index 698397d..75dfa68 100644
--- a/unit-tests/block_t.cc
+++ b/unit-tests/block_t.cc
@@ -169,6 +169,11 @@ TEST(BlockTests, superblocks_can_change_address)
 	{ bm4096::write_ref superblock = bm->superblock(1); }
 }
 
+// This test terminates with g++ 4.8.1.  This is because it erroneously
+// assumes a noexcept(true) specification is present on every declared
+// destructor.  Not a bad idea, but not what the standard says.  Obviously
+// we really shouldn't be throwing in a destructor, but not sure what the
+// correct thing to do is (log the error? put the tm into a 'bad' state?).
 TEST(BlockTests, superblock_must_be_last)
 {
 	bm4096::ptr bm = create_bm<4096>();