This is the mail archive of the gcc-patches@gcc.gnu.org mailing list for the GCC project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: [Patch, fortran] Runtime memory leak checking.


Dear All,

There are clearly some issues with this patch.
(i) Truthfully, I agree with Steve - it is too late for 4.4 and so
this is 4.5 material.
(ii) The -static was an accident - I had scrubbed $LD_LIBRARY_PATH and
was extemporising!
(iii) I don't know what is happening below.
(iv) Manifestly, Joost is right - there is a long way to go with this!

Cheers

Paul

On Sat, Nov 29, 2008 at 9:11 PM, Dominique Dhumieres <dominiq@lps.ens.fr> wrote:
>
>> (1) I think the -static option won't work on Darwin.
>
> Confirmed: I get
>
> [ibook-dhum] f90/bug% gfc -static -fruntime-check=memleaks /opt/gcc/gcc-4.4-work/gcc/testsuite/gfortran.dg/mem_check_1.f90 -L/opt/gcc/gcc4.4w/lib/
> ld_classic: can't locate file for: -lcrt0.o
> collect2: ld returned 1 exit status
>
> without the -static option, I can compile, but I get at runtime:
>
> [ibook-dhum] f90/bug% gfc -fruntime-check=memleaks /opt/gcc/gcc-4.4-work/gcc/testsuite/gfortran.dg/mem_check_1.f90
> [ibook-dhum] f90/bug% a.out
> dyld: Symbol not found: _htab_hash_pointer
>  Referenced from: /opt/gcc/gcc4.4w/lib/libgfortran.3.dylib
>  Expected in: dynamic lookup
>
> Trace/BPT trap
>
> TIA
>
> Dominique
>



-- 
The knack of flying is learning how to throw yourself at the ground and miss.
       --Hitchhikers Guide to the Galaxy


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]