Re: memory leak reported by totalview on some platforms
- From: Fei Liu <fei.liu@xxxxxxxxx>
- Date: Wed, 26 Mar 2008 11:45:09 -0400
Arjen Markus wrote:
On 26 mrt, 02:02, Fei Liu <fei....@xxxxxxxxx> wrote:In this case, it's a fresh automatic object as in the case of the
original code.
Fei- Tekst uit oorspronkelijk bericht niet weergeven -
- Tekst uit oorspronkelijk bericht weergeven -
I am not familiar with Totalview (I know of it, that is
all), but could it be that you are using a F90 compiler
rather than a F95 compiler, as the status of an
uninitialised pointer in F90 is undefined. Totalview
could then see some random memory being associated with
the basep pointer.
One solution you might try: initialise the basep component
in the type definition.
type compos
type(base), pointer :: basep => null()
integer :: id
end type
and similarly in type base.
Regards,
Arjen
I think this is a reasonable solution. Thanks,
Fei
.
- References:
- memory leak reported by totalview on some platforms
- From: Fei Liu
- Re: memory leak reported by totalview on some platforms
- From: Michel Olagnon
- Re: memory leak reported by totalview on some platforms
- From: Fei Liu
- Re: memory leak reported by totalview on some platforms
- From: Arjen Markus
- memory leak reported by totalview on some platforms
- Prev by Date: Re: How to handle code with both Co-arrays and OpenMP
- Next by Date: what is wrong with this code?can someone walk me through this?
- Previous by thread: Re: memory leak reported by totalview on some platforms
- Next by thread: F2003 standard: Can Class(*) be used in generic proogramming?
- Index(es):
Relevant Pages
|
|
