[petsc-users] petsc binary vtk viewer
Jed Brown
jedbrown at mcs.anl.gov
Mon May 6 17:23:20 CDT 2013
Dharmendar Reddy <dharmareddy84 at gmail.com> writes:
>> 32/64-bit values shouldn't matter, but it's possible there is a bug with
>> 64-bit-indices (I don't remember testing it). Is the writing code
>> valgrind-clean? Is it reproducible?
>>
>
> Hello, I ran the code a few times now, I get the same error in paraview.
> I can see that there are no nan's in the data when i look at spreadsheet
> view of the 2D. But nan's show up in plot over line.
What should I do? If you think there is a problem in PETSc code, I'm
afraid I'll need some way to reproduce (test case preferred) or much
more specific information about how it occurs.
> Also, The following is the final output for valgrind. My code is in
> fortran, based on valgrind, i think are no leaks in the program.
>
> ==18978==
> ==18978== HEAP SUMMARY:
> ==18978== in use at exit: 0 bytes in 0 blocks
> ==18978== total heap usage: 0 allocs, 0 frees, 0 bytes allocated
> ==18978==
> ==18978== All heap blocks were freed -- no leaks are possible
> ==18978==
> ==18978== For counts of detected and suppressed errors, rerun with: -v
> ==18978== Use --track-origins=yes to see where uninitialised values come
> from
> ==18978== ERROR SUMMARY: 24076 errors from 1000 contexts (suppressed: 14
> from 9)
> Profiling timer expired
More information about the petsc-users
mailing list