[Dune] [#493] test failure: dune-common/common/test/sllisttest (Attachment added)

[Dune]

THIS IS AN AUTOMATED MESSAGE, DO NOT REPLY.

The following task has a new comment added:

FS#493 - test failure: dune-common/common/test/sllisttest
User who did this - Oliver Sander (sander)

----------
This one is really strange. I could reproduce this using gcc 4.1, 4.2, 4.3.  Elias told me that he originally saw it just using O2 instead of this weird set of options, but I cannot confirm this.

I tried to reduce the test case further but I didn't get very far (new test case is attached). Seemingly innocent actions make the bug go away. For example, I can remove the assertion in line 51 (which passes), and the bug goes away.  Also, when I replace the list object by direct declaration of its data members, the bug goes away.

I am stuck. The test case is still too long to post it as a gcc bug (it still includes poolallocator.hh).  Does someone have an idea how to proceed?  The test case does the following:
- create an empty list
- push_back(1)
- push_front(3)
- pop_front()

Now the first list item should be 1, but this is not so.  Instead, apparently unitialized memory is accessed there.  If the PoolAllocator is replaced by std::allocator everything works fine.

The platform is
Linux andorra 2.6.26-2-amd64 #1 SMP Wed Aug 19 22:33:18 UTC 2009 x86_64 GNU/Linux

----------

One or more files have been attached.

More information can be found at the following URL:
http://www.dune-project.org/flyspray/index.php?do=details&task_id=493#comment1191

You are receiving this message because you have requested it from the Flyspray bugtracking system.  If you did not expect this message or don't want to receive mails in future, you can change your notification settings at the URL shown above.