[dune-pdelab] Run-time errors from the gcc sanitizer

[Christian Engwer]

On Tue, Jun 30, 2015 at 06:08:33PM +0200, Oliver Sander wrote:
> Dear dune-pdelab team,
> 
> I tried running my program du jour with -fsanitize-undefined and gcc 4.9.
> It spits out the following errors:
> 
> /home/sander/dune/dune-pdelab/dune/pdelab/ordering/localorderingbase.hh:20:11: runtime error: load of value 176, which is not a valid value for type 'bool'
> /home/sander/dune/dune-pdelab/dune/pdelab/ordering/localorderingbase.hh:20:11: runtime error: load of value 196, which is not a valid value for type 'bool'
> /home/sander/dune/dune-pdelab/dune/pdelab/ordering/orderingbase.hh:21:11: runtime error: load of value 207, which is not a valid value for type 'bool'
> /home/sander/dune/dune-pdelab/dune/pdelab/ordering/orderingbase.hh:21:11: runtime error: load of value 112, which is not a valid value for type 'bool'
> 
> The exact values change with every new run of the program.  valgrind remains silent.
> 
> The given line numbers do not give any useful information (to me).
> 
> Is that something I should worry about?  Would you be interested in a small test program?

It seems to me that in both classes the _fixed_size bool is never
initialized. Perhaps it's this what gcc is complaining about!?

Christian