Crap, that is totally what is happening.  I am not using the libMesh 
build system; I am using my own, and I did not realize that I needed to 
be including -DDEBUG.

-- Boyce

On 3/14/11 1:55 PM, Roy Stogner wrote:
> That mesh_base.h change should indeed break in crazy crazy ways if
> it's used to build both object files with -DDEBUG and object files
> without -DDEBUG and those object files are then mixed together; the
> presence/lack of a virtual function would probably result in differing
> vtables.
>
> Although I don't understand how the two of you could be accidentally
> mixing different levels of debugging flags, it's actually something
> I'd like to support doing on purpose (since it's often useful to just
> slow down the one particular source file where you want to investigate
> problems. I'll move the function (but not the calls to it) out of the
> ifdef wrappers; from what John's been telling me that should fix this
> bug even if I'm misunderstanding its cause.
> ---
> Roy
>

------------------------------------------------------------------------------
Colocation vs. Managed Hosting
A question and answer guide to determining the best fit
for your organization - today and in the future.
http://p.sf.net/sfu/internap-sfd2d
_______________________________________________
Libmesh-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/libmesh-devel

Reply via email to