Hi Everyone,
I´ve got the following code which gives me the infamous "Unaligned Array" assert in line 3, when trying to add the transformation to the map.

Code: Select all

  roboapp::Timestamp timestamp = model->getTimestamp();
  Eigen::Transform3f transformation  = model->getTransformation();
  incMap[timestamp] = transformation;


incMap ist just a std:map:

Code: Select all

std::map incMap;


and model´s getTransformation just returns some Eigen::Transformation3f :

Code: Select all

Eigen::Transform3f Model::getTransformation() const
{
  return Eigen::Transform3f(Eigen::Matrix4f::Identity() );
}


So it looks like when inserting the Eigen::Transform3f into the map, Operator new is not used, and thus I get the alignment assert. Is there a workaround for this, or am I misunderstanding something?

regards,
Stefan

Svn up and retry please

Probably std::map calls a placement new and until beta5 included this wasn't getting overloaded for Transform. The latest code uses a unique macro EIGEN_MAKE_ALIGNED_OPERATOR_NEW that overloads the placement new as well. So it should fix your issue.

Ok, maybe I should´ve been more specific about my configuration:
I´m using VS2005 and the Eigen2 directly via latest svn.
I still have the problem though :

quick update from IRC until we finish solving this issue...
the problem is that a custom allocator must be used with this map. ei_new_allocator does that but then it has issues of its own.

bjacob wrote:quick update from IRC until we finish solving this issue...
the problem is that a custom allocator must be used with this map. ei_new_allocator does that but then it has issues of its own.

I have just committed "aligned_allocator" which should allow you to store aligned types in a std::map. There is still sometimes a compile-time issue with other STL containers that have a standard-conformant resize() method that passes by value, but I believe this should fix the original issue with std::map like so:

std::map, aligned_allocator > matrixMap;