Did my suggested change not work for you?
Satish
On Thu, 24 Dec 2009, Matthew Knepley wrote:
I spent a bunch of time on this today. This shit is hopelessly broken. It
sucks completely.
I cannot get it to run, nor see why it is causing stack overruns and SEGVs.
If anyone does
not think it
BTW: What linux are you using? ubuntu version? i686 or x86_64? etc...
also try:
arg-name = (char *)MALLOC( strlen(p) + 100 );
satish
On Fri, 25 Dec 2009, Satish Balay wrote:
Did my suggested change not work for you?
Satish
On Thu, 24 Dec 2009, Matthew Knepley wrote:
I spent a
On Fri, Dec 25, 2009 at 10:14 AM, Satish Balay balay at mcs.anl.gov wrote:
Did my suggested change not work for you?
No. It did not even fix the stack smash. I fixed that, but then it SEGV
somewhere else.
Matt
Satish
On Thu, 24 Dec 2009, Matthew Knepley wrote:
I spent a bunch of
Well - perhaps you can try the change to unmodified bfort.
Sure - I don't understatand the bug - and what my suggested change
does. However my observation is: with that change - valgrind log is
clean for me.
Satish
On Fri, 25 Dec 2009, Matthew Knepley wrote:
On Fri, Dec 25, 2009 at 10:14 AM,
Well - normally the first step with detecting the bugs is to report
them to the author - and ask for a fix..
Satish
On Fri, 25 Dec 2009, Matthew Knepley wrote:
I can try, but I still think replacement is the only real alternative. This
is not
able to be debugged, or you would not recommend
Can you send me the valgrind.log - with the patch applied to the
unmodified sowing-1.1.11-a.tar.gz?
Also the command you are using to generate this log?
I've used the following:
valgrind --tool=memcheck -q --log-file=valgrind.log bfort -dir `pwd`/ftn-auto
-ansi -nomsgs -noprofile -anyname
Here is the valgrind for your +100 fix:
knepley at khan:/PETSc3/petsc/petsc-dev/src/mat/utils$ valgrind
/PETSc3/petsc/petsc-dev/linux-gnu-cxx-debug/bin/bfort -dir
/PETSc3/petsc/petsc-dev/src/mat/utils/ftn-auto -mnative -ansi -nomsgs
-noprofile -anyname -mapptr -mpi -mpi2 -ferr -ptrprefix Petsc
On Fri, Dec 25, 2009 at 2:11 PM, Satish Balay balay at mcs.anl.gov wrote:
Are you sure bfort got rebuilt witht he change? I cant get this valgrind
output..
Yes, I am positive. How do I check this? I make a change, rebuild and
install, and
when I am in the debugger the line numbers change to
This does not make any sense to me because it would be a heap violation, not
a stack smash.
Matt
On Mon, Dec 21, 2009 at 4:30 PM, Satish Balay balay at mcs.anl.gov wrote:
[I don't know the correct fix for this - but ] The following change is
getting rid of valgrind messages for me. Maybe
