Hi all,
RBEvaluation makes a direct call to write_header and read_header, and
this seems to be causing a problem.
For example, when I modify ex23 so that it has two variables ("u" and
"v") rather than one, I get an error in rb_evaluation.C:1029 when the
system tries to read in a header file before reading the subsequent
sequence of .xdr files. The stack trace is below; the system is looking
for a variable with name "", whereas it should be "u".
The header is written in rb_evaluation.C:
Xdr header_data(file_name.str(), ENCODE);
sys.write_header(header_data, "", false);
and also read in rb_evaluation.C with:
Xdr header_data(file_name.str(), DECODE);
sys.read_header(header_data, "", false);
I was wondering if there's anything obviously wrong with this usage of
read/write_header? These methods appear to be used in a similar manner
in equation_systems.C. In particular, I can't see why the 2-variable
case triggers an error whereas the 1-variable case works fine?
Many thanks,
Dave
-----------------------------------------------------------------------------------------------------------------
ERROR: variable does not exist in this system!
[0] src/systems/system.C, line 1076, compiled Sep 6 2011 at 22:15:39
terminate called after throwing an instance of 'libMesh::LogicError'
what(): Error in libMesh internal logic
Program received signal SIGABRT, Aborted.
0x00007ffff08ccd05 in raise (sig=6) at
../nptl/sysdeps/unix/sysv/linux/raise.c:64
64 ../nptl/sysdeps/unix/sysv/linux/raise.c: No such file or directory.
in ../nptl/sysdeps/unix/sysv/linux/raise.c
(gdb) bt
#0 0x00007ffff08ccd05 in raise (sig=6) at
../nptl/sysdeps/unix/sysv/linux/raise.c:64
#1 0x00007ffff08d0ab6 in abort () at abort.c:92
#2 0x00007ffff0ce86dd in __gnu_cxx::__verbose_terminate_handler() ()
from /usr/lib/x86_64-linux-gnu/libstdc++.so.6
#3 0x00007ffff6e670ef in libMesh::libmesh_terminate_handler () at
src/base/libmesh.C:200
#4 0x00007ffff0ce6926 in ?? () from
/usr/lib/x86_64-linux-gnu/libstdc++.so.6
#5 0x00007ffff0ce6953 in std::terminate() () from
/usr/lib/x86_64-linux-gnu/libstdc++.so.6
#6 0x00007ffff0ce6a5e in __cxa_throw () from
/usr/lib/x86_64-linux-gnu/libstdc++.so.6
#7 0x00007ffff76bf96f in libMesh::System::variable_number
(this=0x7ea930, var=...) at src/systems/system.C:1076
#8 0x00007ffff76d2d4f in libMesh::System::read_header (this=0x7ea930,
io=..., version=..., read_header=false,
read_additional_data=true, read_legacy_format=false) at
src/systems/system_io.C:232
#9 0x00007ffff7675450 in libMesh::RBEvaluation::read_in_basis_functions
(this=0x7fffffffd920, sys=...,
directory_name=..., read_binary_basis_functions=true) at
src/systems/rb_evaluation.C:1029
#10 0x000000000044c09f in main (argc=1, argv=0x7fffffffe668) at
ex23_vector.C:144
------------------------------------------------------------------------------
Doing More with Less: The Next Generation Virtual Desktop
What are the key obstacles that have prevented many mid-market businesses
from deploying virtual desktops? How do next-generation virtual desktops
provide companies an easier-to-deploy, easier-to-manage and more affordable
virtual desktop model.http://www.accelacomm.com/jaw/sfnl/114/51426474/
_______________________________________________
Libmesh-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/libmesh-devel
