[petsc-dev] Open solaris 64bit printf bug?

[Barry Smith]

  And just to annoy me I cannot get -start_in_debugger to work on that machine. Valgrind has no complaints on a Mac with the examples.

  I've found some miss-use of PetscViewerASCIIPushSynchronized() and %d in parts of plex, I don't see how they could cause this problem but I am fixing them and will push that. Maybe we'll get lucky.

  Barry

> On Sep 3, 2015, at 10:06 AM, Tobin Isaac <tisaac at ices.utexas.edu> wrote:
> 
> 
> Here's a partial diff from http://ftp.mcs.anl.gov/pub/petsc/nightlylogs/archive/2015/09/03/examples_next_arch-opensolaris-misc_n-gage.log:
> 
>    232c232
>    <   field 0 with 2 components
>    ---
>>  field 0 with 0 components
>    234,242c234,242
>    <   (   2) dim  2 offset   0 0.5 0
>    <   (   3) dim  2 offset   2 1 0
>    <   (   4) dim  2 offset   4 0 0.5
>    <   (   5) dim  2 offset   6 0.5 0.5
>    <   (   6) dim  2 offset   8 1 0.5
>    <   (   7) dim  2 offset  10 0 1
>    <   (   8) dim  2 offset  12 0.5 1
>    <   (   9) dim  2 offset  14 0.5 0.25
>    <   (  10) dim  2 offset  16 0.25 0.5
>    ---
>>  (   2) dim  0 offset   2 0.5 0
>>  (   3) dim  0 offset   2 1 0
>>  (   4) dim  0 offset   2 0 0.5
>>  (   5) dim  0 offset   2 0.5 0.5
>>  (   6) dim  0 offset   2 1 0.5
>>  (   7) dim  0 offset   2 0 1
>>  (   8) dim  0 offset   2 0.5 1
>>  (   9) dim  0 offset   2 0.5 0.25
>>  (  10) dim  0 offset   2 0.25 0.5
> 
> The numbers that printf is making 0 (or 2) clearly aren't, because
> they are used to iterate over a section and display its contents.  But
> other PetscInt's are printed fine elsewhere.  Weird.
> 
>  Toby
>