On Mon, Jul 21, 2008 at 3:03 PM, Barry Smith wrote:
>
> Matt,
>
>You have to be careful here. You use PetscMalloc() here, are you positive
> this
> routine will never be called BEFORE PetscMalloc() is setup for (sometime in
> PetscInitialize), or after PetscMalloc()
> is taken down (somewhere
Fixed.
Matt
On Mon, Jul 21, 2008 at 3:32 PM, Barry Smith wrote:
>
> Matt,
>
> While you are at it could you please fix the buggy code in mprint.c?
>
> make PETSC_DIR=/Users/bsmith/Src/petsc-dev-for-fixes
> PETSC_ARCH=arch-icc-ifort
> /Users/bsmith/Src/petsc-dev-for-fixes/arch-icc-ifort/bin/m
Matt,
While you are at it could you please fix the buggy code in mprint.c?
make PETSC_DIR=/Users/bsmith/Src/petsc-dev-for-fixes PETSC_ARCH=arch-
icc-ifort
/Users/bsmith/Src/petsc-dev-for-fixes/arch-icc-ifort/bin/mpicc -o
mprint.o -c -wd1572 -Qoption,cpp,--extended_float_type -g -I/Use
I will check all the occurences of SynchronizedPrintf() in the source.
Matt
On Mon, Jul 21, 2008 at 3:03 PM, Barry Smith wrote:
>
> Matt,
>
>You have to be careful here. You use PetscMalloc() here, are you positive
> this
> routine will never be called BEFORE PetscMalloc() is setup for (s
Pushed a fix. I missed the Viewer when I corrected the raw call. That should
not be separate code.
Matt
On Mon, Jul 21, 2008 at 2:54 PM, Satish Balay wrote:
> Matt - Perhaps ex7 is a different Problem. But it does crash for me.
> And I noticed the following code:
>
>ierr = Pet
Matt,
You have to be careful here. You use PetscMalloc() here, are you
positive this
routine will never be called BEFORE PetscMalloc() is setup for
(sometime in PetscInitialize), or after PetscMalloc()
is taken down (somewhere in PetscFinalize())? Is there someway you can
make sure
Matt - Perhaps ex7 is a different Problem. But it does crash for me.
And I noticed the following code:
>>>
ierr = PetscNew(struct _PrintfQueue,&next);CHKERRQ(ierr);
if (queue) {queue->next = next; queue = next;}
else {queuebase = queue = next;}
queuelength++;
st
I made this change because synchronized printing was cutting off my
stuff. Now the queue is dynamically allocated so it can accomodate
any size string.
I tried ex7 and it runs fine for me, even under valgrind.
Shi, can you reproduce this with a Sieve example?
Matt
On Mon, Jul 21, 2008 at 2:37
Looks like this could be related to changeset 9e3fbe04a926
--> mprint.h <--
- charstring[QUEUESTRINGSIZE];
+ char *string;
So now strings needs to use malloc()/free()?
Matt - you can reproduce this issue with dm/ao/examples/tests/ex7.c
Satish
On Mon, 21 Jul 2008, Satish Balay
-- Forwarded message --
Date: Sun, 20 Jul 2008 22:39:13 -0700 (PDT)
From: Shi Jin
Subject: problem with PetscSynchronizedFPrintf
To: petsc-dev at mcs.anl.gov
Hi,
I recently updated my petsc-dev and found my previously working code is having
trouble running in parallel. I've nar
10 matches
Mail list logo
