Has anyone using libMesh seen invalid characters in string files output in
the Exodus files?
I'm seeing strings like this in several of our output files (output is from
"ncdump")
name_glo_var =
"integral\000\340\000\000\277\367\220\276\f\"\203\254\277\367\220\276\f\"b>"
;
Clearly there is garbage after the variable named "Integral" but the first
escaped byte is always zero, or at least that's what it looks like to me.
This may be a bug in the exodus writer or perhaps we need to clear some
buffer that we aren't clearing. We don't always see it but is kind of
nasty. Just seeing if anyone else has encountered this before.
Cody
------------------------------------------------------------------------------
Dive into the World of Parallel Programming The Go Parallel Website, sponsored
by Intel and developed in partnership with Slashdot Media, is your hub for all
things parallel software development, from weekly thought leadership blogs to
news, videos, case studies, tutorials and more. Take a look and join the
conversation now. http://goparallel.sourceforge.net/
_______________________________________________
Libmesh-devel mailing list
Libmesh-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/libmesh-devel
