--- Comment #5 from dfranke at gcc dot gnu dot org 2008-07-30 12:07 ---
Closing as WORKSFORME - the reporter can not reproduce the problem (see
PR36157, comment #6).
--
dfranke at gcc dot gnu dot org changed:
What|Removed |Added
---
--- Comment #4 from michael dot a dot richmond at nasa dot gov 2008-05-11
19:56 ---
(In reply to comment #3)
> Use the following
>
> valgrind --leak-check=full f951 pr36139.f90
I downloaded http://valgrind.org/downloads/valgrind-3.3.0.tar.bz2 and attempted
to build valgrind on HP-PA
--- Comment #3 from jvdelisle at gcc dot gnu dot org 2008-05-11 17:34
---
Use the following
valgrind --leak-check=full f951 pr36139.f90
In my case f951 is in my search path as a link:
f951 -> /home/jerry/gcc/obj44/gcc/f951
obj44 is the build directory
--
http://gcc.gnu.org/bug
--- Comment #2 from michael dot a dot richmond at nasa dot gov 2008-05-11
17:16 ---
(In reply to comment #1)
> Though I do not get segfault, I can confirm valgrind errors.
The segfault does not occur in the snapshot of May 9. I suspect the valgrind
errors occur on multiple platforms, b
--- Comment #1 from jvdelisle at gcc dot gnu dot org 2008-05-10 15:03
---
Though I do not get segfault, I can confirm valgrind errors.
==3660== 158 bytes in 1 blocks are definitely lost in loss record 3 of 9
==3660==at 0x4A04D1F: calloc (vg_replace_malloc.c:279)
==3660==by 0xB3
