On Mon, Dec 14, 2015 at 11:06 PM, Timothée Nicolas <
timothee.nico...@gmail.com> wrote:
> There is a diference in valgrind indeed between the two. It seems to be
> clean on my desktop Mac OS X but not on the cluster. I'll try to see what's
> causing this. I still don't understand well what's causi
There is a diference in valgrind indeed between the two. It seems to be
clean on my desktop Mac OS X but not on the cluster. I'll try to see what's
causing this. I still don't understand well what's causing memory leaks in
the case where all PETSc objects are freed correctly (as can pbe checked
wit
On Mon, 14 Dec 2015, Eric Chamberland wrote:
> Le 2015-12-14 11:09, Jed Brown a écrit :
> > Eric Chamberland writes:
> > > I see. In fact, I was thinking of 3.6.4.rc1, 3.6.4.rc2, then 3.6.4,
> > > followed by 3.6.5.rc1, 3.6.5.rc2, then 3.6.5, etc...
> >
> > Those patch releases are only bug fixe
Le 2015-12-14 11:09, Jed Brown a écrit :
Eric Chamberland writes:
I see. In fact, I was thinking of 3.6.4.rc1, 3.6.4.rc2, then 3.6.4,
followed by 3.6.5.rc1, 3.6.5.rc2, then 3.6.5, etc...
Those patch releases are only bug fixes, not new features. I'm not
aware of PETSc having a problem of in
Eric Chamberland writes:
> I see. In fact, I was thinking of 3.6.4.rc1, 3.6.4.rc2, then 3.6.4,
> followed by 3.6.5.rc1, 3.6.5.rc2, then 3.6.5, etc...
Those patch releases are only bug fixes, not new features. I'm not
aware of PETSc having a problem of introducing bugs in these patch
releases a
Le 2015-12-13 22:12, Satish Balay a écrit :
On Sat, 12 Dec 2015, Eric Chamberland wrote:
Le 2015-12-11 23:43, Satish Balay a écrit :
We do autmoatically generate tarballs everynight - its avaliable at:
http://ftp.mcs.anl.gov/pub/petsc/petsc-master.tar.gz [but we don't
maintain snapshots - i.e
OK, I'll try that, thx
2015-12-14 17:38 GMT+09:00 Dave May :
> You have the configure line, so it should be relatively straight forward
> to configure / build petsc in your home directory.
>
>
> On 14 December 2015 at 09:34, Timothée Nicolas > wrote:
>
>> OK, The problem is that I don't think I
You have the configure line, so it should be relatively straight forward to
configure / build petsc in your home directory.
On 14 December 2015 at 09:34, Timothée Nicolas
wrote:
> OK, The problem is that I don't think I can change this easily as far as
> the cluster is concerned. I obtain acces
OK, The problem is that I don't think I can change this easily as far as
the cluster is concerned. I obtain access to petsc by loading the petsc
module, and even if I have a few choices, I don't see any debug builds...
2015-12-14 17:26 GMT+09:00 Dave May :
>
>
> On Monday, 14 December 2015, Timot
On Monday, 14 December 2015, Timothée Nicolas > wrote:
> Hum, OK. I use FORTRAN by the way. Is your comment still valid ?
>
No. Fortran compilers init variables to zero.
In this case, I would run a debug build on your OSX machine through
valgrind and make sure it is clean.
Other obvious thing to
Hum, OK. I use FORTRAN by the way. Is your comment still valid ? I'll check
anyway, but I thought I had been careful about this sort of things.
Also, I thought the problem on Mac OS X may have been due to the fact I
used the version with debugging on, so I rerun configure with
--with-debugging=no,
One suggestion is you have some uninitialized variables in your pcshell.
Despite your arch being called "debug", your configure options indicate you
have turned debugging off.
C standard doesn't prescribe how uninit variables should be treated - the
behavior is labelled as undefined. As a result,
12 matches
Mail list logo
