> By the way, the line numbers you quoted are already off from master. > If you are serious about doing development, you should really start > using git and a libmesh fork. Then we can actually look at your > branch, see the entire diff, and have a better idea of where bugs > might be.
This times a thousand. A public fork from which we can replicate any bugs is invaluable, especially for things like a missing parent() where the assertion itself is only useful for catching an error early but where you really need to be able to see the stack trace and examine variables to figure out *why* the error is there. --- Roy ------------------------------------------------------------------------------ HPCC Systems Open Source Big Data Platform from LexisNexis Risk Solutions Find What Matters Most in Your Big Data with HPCC Systems Open Source. Fast. Scalable. Simple. Ideal for Dirty Data. Leverages Graph Analysis for Fast Processing & Easy Data Exploration http://p.sf.net/sfu/hpccsystems _______________________________________________ Libmesh-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/libmesh-users
