On Tue, Dec 10, 2013 at 8:25 AM, Andrew Davis <andrew....@gmail.com> wrote: > Hi all, > > I'm observing some strange behavior using the > System::point_valuefunction. I have a system of two variables (say > "u" and "v"), each added > using the function > > system.add_variable(name, libMeshEnums::Order); > > if they have the same libMesh::Enums::Order, there is no problem. However, > if they have different orders I am noticing that system.point_value(varNum, > point) does not always work properly. > > If the first one is lower order: > > system.point_value(0, point) is correct > system.point_value(1, point) is wrong
Wrong how? Does it return 0? Is this is serial or parallel? > if the first one is higher order: > > system.point_value(0, point) is correct > system.point_value(1, point) results in a seg. fault That certainly sounds like a bug... Roy initially wrote this code quite a while ago (Feb 2010) so he may have a better suggestion, but can you try running in debug mode, preferably configured with --enable-tracefiles, and see if you either hit an assert or generate a useful stack trace? -- John ------------------------------------------------------------------------------ Rapidly troubleshoot problems before they affect your business. Most IT organizations don't have a clear picture of how application performance affects their revenue. With AppDynamics, you get 100% visibility into your Java,.NET, & PHP application. Start your 15-day FREE TRIAL of AppDynamics Pro! http://pubads.g.doubleclick.net/gampad/clk?id=84349831&iu=/4140/ostg.clktrk _______________________________________________ Libmesh-users mailing list Libmesh-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/libmesh-users
