Just a warning to any of you out there using OSX with the Intel compilers... DON'T use optimization flags when compiling in debug mode! Things really don't work properly.... and it _will_ cause you to lose a day of work while you figure out what the hell is going on! Trust me...
For the libMesh developers.... here's what was happening: The assert around line 1352 of dof_map.C was failing. The reason? It turns out that somehow a call to FE<3, LAGRANGE>::n_dofs() was _actually_ calling FE<3, XYZ>::n_dofs() !!!!!!!!!!!!!!!! Seriously. I don't know what the hell the compiler was thinking... but just turning off optimization flags fixed the issue. As to why I had optimization flags on while I was debugging... it's just because I'm lazy and I have optimization flags set in environment variables for ease.... it seems like laziness is paying off less and less these days.... ;-) Note that this isn't the cause of my Hex27 woes I emailed about yesterday... this is something I ran into when trying to track down the Hex27 issue.... Now back to tracking down _other_ bugs.... Derek ------------------------------------------------------------------------------ Stay on top of everything new and different, both inside and around Java (TM) technology - register by April 22, and save $200 on the JavaOne (SM) conference, June 2-5, 2009, San Francisco. 300 plus technical and hands-on sessions. Register today. Use priority code J9JMT32. http://p.sf.net/sfu/p _______________________________________________ Libmesh-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/libmesh-users
