Re: Possible heap problem on Windows, help sought

[Ludovic Brenta <ludovic@ludovic-brenta.org>]

Niklas Holsti writes:
> I'm grateful for your advice. Thanks to the Ada run-time checks it
> has been a while since I had to fight with this kind of bug, but I
> hope it will come back to me -- and then go away again :-)

Same here; for the past coupld of months, I've been trying, on and
off, to fight a nasty heap corruption bug in GPS 3.1.3, 4.0.0 and now
4.1.1.  I've documented the various symptoms in Debian bugs #393636,
#400876 and #400883.  I realised that my skills are insufficient for
such a large-scale undertaking; Valgrind detected more that 10 million
errors during a short run of GPS, most of which in Python or GTK+
libraries, and not all of which are necessarily serious.  Any advice?

Today I replaced one instance of Unchecked_Deallocation with a no-op
and behold, GPS no longer crashes.  Obviously, it leaks, but that's
not as bad as crashing or hanging.  Because there was nothing
obviously wrong with the Unchecked_Deallocation that I removed, I
suspect there is still some heap corruption going on unnoticed.  See
my latest comment on #400876.

I'm thinking maybe I should instrument access types to use debug
pools, but there are too many of them.

That's obviously not on Windows; sorry for hijacking your thread,
Niklas :)

-- 
Ludovic Brenta.