Re: [Valgrind-developers] aspace mgr woes

[Florian K. <fl...@ei...>]

On 04.02.2015 12:08, Julian Seward wrote:

> The problematic ones have the form
> 
>    seg = VG_(am_find_nsegment)(...)
>    do dynamic memory allocation
>    assume seg is still valid
> 
> so your proposal would tidy up the NSegment interface a bit, but I don't
> think it addresses the underlying issue.  But I could be misunderstanding
> what you intend.

Let me quote what I said:

  ...let's make the definition of NSegment private to m_aspacemgr.
  If we can do this without introducing new issues, when we would have
  eliminated the problem.

In other words, there will be no pointers to NSegment available outside
m_aspacemgr.

This will require rewriting some code like the snippet above,
introducing new functions, moving stuff around, etc..

   Florian